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

Nuno Magalhães nunomagalhaes at
Mon Mar 24 10:32:45 UTC 2014

On Mon, Mar 24, 2014 at 2:11 AM, Kunal Pariani <kunalvjti at> wrote:
> So can this be that the upstream is sending the right header (because it
> works fine when there is no space in the filename) but nginx is parsing it
> incorrectly ?

Use the web developer tools in your browser to see the header and/or
try encoding the filename (not sure about this last one).
Or GET it yourself with telnet or something.


More information about the nginx mailing list