Re: Luasocket 2.0: socket.http.request using POST

[Diego Nehab <diego@...>]

Hi,

I wouldn't call this a bug. It is a feature request. A bug is something
that behaves differently from specification.

The simple API simply does not support the definition of a content-type
header (call it oversight).  The content-length header is a completely
different story. It *has* to be there. When I wrote the code, the most
popular servers did not accept accept chunked posts. Besides it is *not*
ambiguous at all. Content-type, on the other hand, is ambiguous.
Why should I define it as being application/x-www-form-urlencoded
instead of, say, multipart/mixed? Is it really more common?

Regards,
Diego.