id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	uname	nginx_version
264	ngx_http_parse.c does'not like LFCR	Martin Loehnertz		"I tried to use the scgi-lib from 
http://www.xamuel.com/scgilib/
and ran into a problem of malformed headers from the upstream server.
I tracked it back to the fact that in the example code from xamuel.com they send
\n\r instead of \r\n as end of line marker.
Replacing this DOS Madness by a normal Unix \n fixed the problem.

Still I think the following code found throughout ngx_http_parse.c is susceptible to this problem
and there does not seem to be a standard forbidding \n\r. So a minor correction might help to prevent further complains.


case CR:
                r->http_minor = 9;
                state = sw_almost_done;
                break;
case LF:
                r->http_minor = 9;
                goto done;
"	enhancement	closed	minor		nginx-core	1.2.x	invalid	parse headers		Linux <my server ip> 2.6.32-028stab099.3 #1 SMP Wed Mar 7 15:20:22 MSK 2012 x86_64 GNU/Linux	"nginx version: nginx/1.2.5
built by gcc 4.4.5 (Debian 4.4.5-8)
TLS SNI support enabled
configure arguments: --user=www-data --group=www-data --with-http_ssl_module --without-http_geo_module --without-http_memcached_module --without-http_split_clients_module --without-http_ssi_module --without-http_uwsgi_module --with-ipv6 --with-http_sub_module --without-http_fastcgi_module"