Allow no body when Content-Length = 0

[lhigueragamboa]

The HTTP spec is ambiguous in determining if a request could have no body when the method is POST, PUT, or PATCH. Some popular HTTP server, like nginx, adopt the policy that a request of the aforementioned methods with no body is allowed if and only if it has the header Content-Length set to 0.

It makes sense not to try to marshal the body when Content-Length has that value.

I understand that an empty body is not the same as no body, and this is why I said the spec is ambiguous. Even though a request of such methods with no body might be unRESTful it is useful for implementing "actions".

Would you consider merging this?

Regards,
Alfonso.

[pjvds]

Is there any reason this is not merged?

[mihasya]

I don't have too strong an opinion, but if that matches nginx's behavior, we can probably merge it without too much fuss. We've definitely worked around this issue at Opsmatic by passing a {} body, so I'm sympathetic to it.

@rcrowley @wadey any strong thoughts on this?

Also, rebase would be much appreciated so that the merge can be done automatically /cc @lhigueragamboa

[willfaught]

I would find this useful as well.