-
Notifications
You must be signed in to change notification settings - Fork 439
Different amqp handle props in different manner. #719
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This behavior is expected. AMQP sends properties as a special header called "application_headers". |
@makasim Sorry, but you do not get me. considering following code: $headers = [
'reply_to' => $replyToQueue->getQueueName(),
'correlation_id' => Uuid::uuid4()->toString()
];
$message = $this->context->createMessage(
json_encode($data),
[], // props
$headers
); when using Enqueue\AmqpBunny\AmqpConnectionFactory => message ( seems to be not ok ): when using Enqueue\AmqpLib\AmqpConnectionFactory => message is different ( seems to be ok ) I expect them to be same in all implementations! |
Agree, have you found out why this happens? |
I belive it's due to internal implementation of bunny lib |
closing than, should be addressed in bunny repo. |
Actual result:
in amqp bunny transport props are put into headers.application_headers
in ampq-lib transport, props are put into headers
Expected result:
I can see props next to headers, not injected into headers key.
If that's expected result - then someone can please explain me why?
The text was updated successfully, but these errors were encountered: