No ability to specify JSON encoding when publishing about pyrabbit HOT 1 CLOSED

You probably want the AMQP headers exposed, but this 'publish' command doesn't use the AMQP protocol. It's a POST to a web server. Let me know if I've misunderstood, or give me s'more details on the use case so I can be more useful (or submit a pull request!). Here's the doc for the 'publish' endpoint of the HTTP management api that pyrabbit talks to:

Publish a message to a given exchange. You will need a body looking something like:

{"properties":{},"routing_key":"my key","payload":"my body","payload_encoding":"string"}

All keys are mandatory. The payload_encoding key should be either "string" (in which case the payload will be taken to be the UTF-8 encoding of the payload field) or "base64" (in which case the payload field is taken to be base64 encoded).
If the message is published successfully, the response will look like:

{"routed": true}

routed will be true if the message was sent to at least one queue.

Please note that the publish / get paths in the HTTP API are intended for injecting test messages, diagnostics etc - they do not implement reliable delivery and so should be treated as a sysadmin's tool rather than a general API for messaging.

from pyrabbit.