HTTP status code bug?

[double]

Hello,

The browser hits a non-existing file. An "error_page" points
to a fastcgi-application. The fastcgi thinks this is not an error
and explicit sets: "Status: 200" or "Status: 302", ...

One would expect that the fastcgi can overwrite the status-code.

E.g.: http://www.domain.name/media/id12345
nginx returns 404, regardless of the fastcgi.


http {
    server {
        listen          80;
        server_name     www.domain.name;
        error_page      404 /index.cgi;
        location / {
            index           index.cgi;                   
            fastcgi_pass    unix:/var/run/fastcgi/dispatch.sock;
            ....;        
        }                                                          
        location ^~ /media/ {                              
            alias /var/www/media/;            
        }                                                          
    }
}


Thanks
Marcus

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,50668,50668#msg-50668