10 messages in ru.sysoev.nginxRe: Empty server name argument - Can'...
FromSent OnAttachments
Luigi PerrotiAug 28, 2008 1:35 am 
Igor SysoevAug 28, 2008 1:56 am 
Luigi PerrotiAug 28, 2008 3:46 am 
Igor SysoevAug 28, 2008 3:48 am 
Luigi PerrotiAug 28, 2008 4:20 am 
Igor SysoevAug 28, 2008 4:33 am 
Luigi PerrotiAug 28, 2008 5:05 am 
Igor SysoevAug 28, 2008 5:16 am 
Luigi PerrotiAug 28, 2008 6:00 am 
Igor SysoevAug 28, 2008 6:05 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Empty server name argument - Can't get it to workActions...
From:Luigi Perroti (luig@public.gmane.org)
Date:Aug 28, 2008 6:00:40 am
List:ru.sysoev.nginx

On Thu, Aug 28, 2008 at 2:17 PM, Igor Sysoev
<is-G@public.gmane.org> 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 too.

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 :)

-Luigi