Hi,
> I have nginx set as a reverse proxy for a mail server and it throws > this 502 (invalid header) error while trying to fetch a file with a > space in the filename. Any clues on where is this bug in the nginx code? Prior to jumping to conlusion about bugs in nginx, how does this response header actually look like? Section 19.5.1 in RFC2616 [1] mandates the content of the filename-parm needs to be a quoted string: > filename-parm = "filename" "=" quoted-string > [...] > An example is > Content-Disposition: attachment; filename="fname.ext" Does your response header correctly quote the filename? Regards, Lukas [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html#sec19.5.1 _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
