Hey there! Let's work through why your Headers Exchange isn't routing messages to the right queues as expected—Headers exchanges are powerful but have a few easy-to-miss details that can trip you up, so let's break this down.

Common Causes & Fixes #

1. Double-Check Your x-match Parameter Behavior #

You mentioned setting x-match:all—this is the linchpin of how Headers Exchanges evaluate matches, so it’s critical to get right:

• When x-match:all is set on a queue binding, every header parameter in the binding must exactly match the message's headers for the message to land in that queue. For example, if a queue is bound with format:pdf + type:report and x-match:all, a message only carrying format:pdf won’t make it to that queue.
• If you want any queue with a format:pdf header parameter to receive the message, those queues should use x-match:any (or only bind with format:pdf and x-match:all if that’s the only parameter required).

2. Verify Header Spelling & Case Sensitivity #

Headers in AMQP implementations are case-sensitive, and even tiny mismatches will break routing:

• Ensure the header key in your message exactly matches the one used in the queue binding (e.g., format:pdf vs. Format:PDF or format:PDF won’t count as a match).
• Check value types too—if you bound the queue with a string value pdf, don’t send a numeric 1 or boolean true for the format header.

3. Confirm Queue Bindings Include All Required Parameters #

When binding a queue to the Headers Exchange, don’t forget to explicitly set both your target headers and the x-match parameter. Some clients don’t set x-match by default, which can lead to silent failures—without it, the exchange might not apply any matching logic at all.

4. Test with Simplified Setups #

To narrow down the issue quickly:

• Create a test queue bound only to format:pdf with x-match:all.
• Publish a message with just the format:pdf header.
• If this works, gradually add other header parameters to the binding or message to see when routing breaks—this will help you isolate conflicting or misconfigured settings.

内容的提问来源于stack exchange，提问作者Matheus Medeiros