> I guess the irregular response comes from your mod_perl backend? Aha, from ngrep listening on port 8080 responding to nginx, it is indeed missing the description: T 10.200.1.59:8080 -> 10.200.1.59:57990 HTTP/1.1 404..Server: Apache/2.2.16 (Debian) mod_perl/2.0.4 Perl/v5.10.1 If apache is in the middle layer, instead of nginx, it looks like apache fills in the status line Tby kgoess - Nginx Mailing List - English
We're using nginx as a middle layer in front of our application server (mod_perl). When mod_perl returns an error page, the HTTP status line is missing the "reason phrase" after the status code, like "Not Found", e.g. HTTP/1.1 404 Server: nginx/1.2.1 ...etc should be HTTP/1.1 404 Not Found ...etc... AFAICT, the HTTP spec requires at least a space after the statuby kgoess - Nginx Mailing List - English