nginx/1.3.2 - 4xx responses are returned without HTTP headers, bug?
Sjon Hortensius
sjon at react.nl
Mon Jul 9 08:41:19 UTC 2012
Hi,
I think I stumbled upon a bug in nginx but I would like to get someone
else's opinion on this.
It seems all 4xx errors are not prefixed by headers in HTTP responses. I
have a simple test-script in bash which you can run to verify this behavior:
function req { echo -n "GET /bugtest?id="; for i in `seq 15000 17100` ;
do echo -n "%7C$i" ; done ; echo -en "HTTP/1.1\nUser-Agent:
Mozilla/5.0\nConnection: Close\nHost: wiki.nginx.org\r\n\r\n" ; } ; req
| nc wiki.nginx.org 80
I can also reproduce this for other 4xx responses. My interpretation of
the RFC is that this is unwanted, see
http://tools.ietf.org/html/rfc2616#section-6.1
If this is not the appropriate place to report this please let me know
as I couldn't find a better place to report this.
--
Regards,
Sjon Hortensius
| React B.V.
| http://www.react.nl
| Julianastraat 30
| 2012 ES, Haarlem
| 023 553 90 00
More information about the nginx
mailing list