13 messages in ru.sysoev.nginxRe: Client closed keepalive connection
FromSent OnAttachments
Wilson BilkovichApr 27, 2007 10:39 am 
Igor SysoevApr 27, 2007 10:52 am 
Wilson BilkovichApr 27, 2007 11:11 am 
Igor SysoevApr 27, 2007 11:17 am 
Wilson BilkovichApr 27, 2007 11:22 am 
Igor SysoevApr 27, 2007 11:33 am 
Wilson BilkovichApr 27, 2007 11:46 am 
Cliff WellsApr 27, 2007 9:10 pm 
Igor SysoevApr 27, 2007 11:47 pm 
Wilson BilkovichApr 28, 2007 10:01 am 
Igor SysoevApr 28, 2007 11:46 am 
Wilson BilkovichApr 28, 2007 1:35 pm 
Igor SysoevApr 29, 2007 7:03 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: Client closed keepalive connectionActions...
From:Wilson Bilkovich (wils@public.gmane.org)
Date:Apr 28, 2007 10:01:53 am
List:ru.sysoev.nginx

On 4/28/07, Igor Sysoev <is-G@public.gmane.org> wrote:

On Fri, Apr 27, 2007 at 09:10:47PM -0700, Cliff Wells wrote:

On Fri, 2007-04-27 at 21:53 +0400, Igor Sysoev wrote:

Does the client do POST and pass "Expect: continue" ? nginx does not support "Expect: continue/100 Continue" dialog because current browsers still do not support it (at least I never see).

I'm not aware of any browsers that support "Expect: continue", however there are some tools and libraries that do (curl/libcurl for one).

As for me, the main use of "Expect: continue/100 Continue" dialog is the request body limitation. I had even written article (sorry, in Russian) "Why it's impossible to limit correctly the uploaded file size": http://sysoev.ru/web/upload.html

The problem is that browsers do not read server response until they will send whole request body. If server will close connection before they have sent body, the browsers issue some network or common error, that has no relation to the "413 Request Entity Too Large" error.

OK. I've disabled the "100 Continue" piece of the response, and I am still seeing these error messages. Is there something else that could cause them?