Empty server name argument - Can't get it to work

Luigi Perroti luigi.perroti at googlemail.com
Thu Aug 28 17:01:03 MSD 2008

On Thu, Aug 28, 2008 at 2:17 PM, Igor Sysoev <is at rambler-co.ru> wrote:

> nginx should trigger a 400 error. Do you mean that request that was passed
> to fastcgi should return 200 or so ?

No, you're right. Indeed nginx should return a 400 error code by
default, it is quite logical. I suppose this must be what the RFC says

I just didn't think that it was still possible to override this
behaviour with the fastcgi server response.
Moreover setting recursive_error_pages to on permits to achieve even
more complex configurations.
These are very useful features indeed.

Admittedly my requirements are quite bizarre, still I'm happy to see
that nginx can easily accommodate them :)


More information about the nginx mailing list