Whoopsy, I forgot to address the other (more important) bug I encountered:
* Content type is only specified for messages published when the
amqp_persistent_msg configuration option is specified. This information
should always be applied to describe the payload of the message.
* Modified the content type declaration to "application/json" in line with
RFC4627.
The second change may cause issues in clients relying on the content type flag
being output already - so I can understand why this might not be adopted.
That being said, making the change should improve compatability with tools
that correctly interpret known MIME types.
This patch is designed to be applied on top of my previous one.
Cheers :)
Will Dowling
contentfix.patch
Description: Binary data
_______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
