-
-
Notifications
You must be signed in to change notification settings - Fork 257
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
Feature requeset: setting message headers #372
Comments
@norberto-e-888 This could be achieved during the publish using |
Thanks @underfisk for super fast turn around to help out norberto. This is available now in Let us know if it accomplishes your goals |
Thanks a lot for the super fast support. There is just one thing I forgot to mention, our use case requires not only to set headers on publish but also on message re-queueing, meaning when we return and instance of Nack(true). Any ideas on how we might achieve this? |
@norberto-e-888 After testing for a while it seems that the message that is consumed is simply forward but if you wish to customize the error behavior you can do that and provide your custom error handler using |
@underfisk Looking at the args of |
Hi,
At my company we have a use case for writing to the message headers to set the following properties:
'x-retry': counter of retries attempts
'x-retry-limit': limit number of retry attempts
'x-delay': number of milliseconds the message should be delayed
could I get some guidance on how this might be achieved using the underlying amqp client, so I can potentially contribute said functionality in case the core team is busy. It is quite urgent for us...
Thank you
The text was updated successfully, but these errors were encountered: