nginx throws a 502 (invalid header) when downloading a file attachment if filename has a space character

Lukas Tribus luky-37 at
Mon Mar 24 21:47:31 UTC 2014

> Never mind there's nothing wrong with nginx here. 
> It was one of the response headers sent by an upstream server  
> (mainly Content-Description: 2013923 10H56M56S633_PV.doc�) including  
> this non-ascii char '?' which the nginx didn't like and hence flagged  
> it saying that it received an invalid header. 

Thanks for confirming.

Nginx does the right thing here, headers must not contain non-ascii chars
per RFC.



More information about the nginx mailing list