Crash (libc-triggered SIGABRT) with empty receiver body

[slact]

Sending an empty-bodied (no content-length or content-length: 0 header) request to a receiver location crashes the worker process hard.

[slact]

Empty-bodied sender requests now queue up an empty message, as expected.

[BrianTheCoder]

Shouldn't empty messages just be ignored? No need to overload the queue if its not needed

[slact]

I figure, in RESTful terms, the resource represented by the sender url is the "last message on this channel". POSTing to this resource would seem to warrant the enqueuing of a message, even if it is an empty one.

Also, how might empty messages otherwise be sent?

[BrianTheCoder]

Well I guess my big question is why would you send an empty message. I would think that having a message would be required for the post to be valid