Ok, correction: this isn't a bug. When you send a completly illegal request header (you can't have spaces in the url, just url encoded space), nginx can't read the HTTP version (GET http://zedshaw.com/this has spaces in it.txt HTTP/1.1). By that nginx thinks it is a pre 1.0 HTTP request (0.9), and then the server shouldn't sent headers. So what nginx doing is completly logical and correct on thisby paul@soulbase.nl - Ideas and Feature Requests
This looks more like a bug. Stable release does it do too, not that any normal browser allows spaces in urls (they will be encoded).by paul@soulbase.nl - Ideas and Feature Requests