diff options
| author | CA Meijer <[email protected]> | 2013-03-02 06:48:04 +0200 |
|---|---|---|
| committer | CA Meijer <[email protected]> | 2013-03-02 06:48:04 +0200 |
| commit | 1932aa2bf42bdee119c9a7b9e1a7a1a7e627be15 (patch) | |
| tree | 2ebb384d4c3a3967d5893a452267ed1ae5bbba43 /system/doc/design_principles/clientserver.gif | |
| parent | 8deb96fb1d017307e22d2ab88968b9ef9f1b71d0 (diff) | |
| download | otp-1932aa2bf42bdee119c9a7b9e1a7a1a7e627be15.tar.gz otp-1932aa2bf42bdee119c9a7b9e1a7a1a7e627be15.tar.bz2 otp-1932aa2bf42bdee119c9a7b9e1a7a1a7e627be15.zip | |
Fix http_request:http_headers/1 to send content-length when length is zero
In R16B01, the http_request:http_headers/1 function removes the content-length
field from the HTTP headers if the content length is zero. This results in
some (perhaps many) HTTP servers rejecting POSTs and PUTs without data with
a 411 status word. From RFC2616, section 14.13: "Any Content-Length greater than
or EQUAL to zero is a valid value".
Diffstat (limited to 'system/doc/design_principles/clientserver.gif')
0 files changed, 0 insertions, 0 deletions