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