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:Igor Sysoev (is-G@public.gmane.org)
Date:Aug 28, 2008 6:05:38 am
List:ru.sysoev.nginx

On Thu, Aug 28, 2008 at 03:01:03PM +0200, Luigi Perroti wrote:

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.

Fastcgi may ovverride 400 code only if

error_page 400 = /400.html;

In case of error_page 400 /400.html;

nginx will send 400 anyway.

-- Igor Sysoev http://sysoev.ru/en/