What debugs should i enable & how to see these response headers ? I do see
this error though.

2014/03/03 14:04:32 [error] 11259#0: *6 upstream sent invalid header
while reading response header from upstream, client: 127.0.0.1,
server: xxx.default, request: "GET
/service/home/~/?auth=co&loc=en_GB&id=259&part=3 HTTP/1.1", upstream:
"https://127.0.1.1:8443/service/home/~/?auth=co&loc=en_GB&id=259&part=3",
host: "xxx", referrer: "https://xxx/ https://server.zimbra.com/"

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 ?

Thanks
-Kunal
On Sun, Mar 23, 2014 at 5:06 PM, Lukas Tribus <luky-37@hotmail.com> wrote:

> 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
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx