httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Covener <>
Subject Re: [users@httpd] cgi-bin disconnecting upload
Date Fri, 06 Dec 2013 14:31:30 GMT
On Fri, Dec 6, 2013 at 9:24 AM, Andreas Frisch
<> wrote:
>> > or keep apache from sending the 100 - continue statement right away?
>> What would it do instead?
> Ιf it didn't send the continue at all, then at least the client side could
> detect a timeout and interrupt the upload itself rather than just keep
> sending data forever that apache has to discard.

Under what criteria, missing Content-Length? You can probably set that
up more directly w/ e.g. mod_rewrite.

If a 100-continue isn't answered, a client could just as well send it
the body anyway:

Because of the presence of older implementations, the protocol allows
   ambiguous situations in which a client may send "Expect: 100-
   continue" without receiving either a 417 (Expectation Failed) status
   or a 100 (Continue) status. Therefore, when a client sends this
   header field to an origin server (possibly via a proxy) from which it
   has never seen a 100 (Continue) status, the client SHOULD NOT wait
   for an indefinite period before sending the request body.

Eric Covener

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message