<div dir="ltr"><div><div>Hi Steve,<br><br>If you want to wildcard a header property, just don&#39;t include it as part of the binding to your headers exchange.  i.e. you have the following header properties:  &quot;colour&quot; and &quot;animal&quot;.  So if you want messages where &quot;animal&quot;=&quot;rabbit&quot; and &quot;colour&quot;=&quot;*&quot;, then don&#39;t include &quot;colour&quot; as part of your binding -- just include &quot;animal&quot;=&quot;rabbit&quot;.  That will give you all &quot;rabbit&quot; messages regardless of colour.<br>
<br></div>Or did I misunderstand your requirements?<br><br></div><div>Regards,<br></div>Dan<br><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 11, 2013 at 1:23 PM, Steve Valaitis <span dir="ltr">&lt;<a href="mailto:steve@digitalnothing.com" target="_blank">steve@digitalnothing.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is there any way to use wildcards right now with header exchange<br>
values? If there isn&#39;t, does anyone know of plans to implement them,<br>
or to allow routing keys to be used in conjunction with header<br>
exchanges?<br>
<br>
Thanks,<br>
Steve<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br><br clear="all"><div><br></div><br>
</div></div>