httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Malo>
Subject Re: [users@httpd] suppressing HTTP 100 continue
Date Fri, 17 Aug 2007 07:58:57 GMT
* Jimmy Lee wrote: 

> I'm working with some devices that can't handle 100 continues.
> Is there a way to apply filters to apache to stop it from sending HTTP
> 100? Or is the only way to hack the base code?

RFC 2616 (8.2.3):

> An origin server SHOULD NOT send a 100 (Continue) response if
>         the request message does not include an Expect request-header
>         field with the "100-continue" expectation, and MUST NOT send a
>         100 (Continue) response if such a request comes from an HTTP/1.0
>         (or earlier) client. There is an exception to this rule: for
>         compatibility with RFC 2068, a server MAY send a 100 (Continue)
>         status in response to an HTTP/1.1 PUT or POST request that does
>         not include an Expect request-header field with the "100-
>         continue" expectation. This exception, the purpose of which is
>         to minimize any client processing delays associated with an
>         undeclared wait for 100 (Continue) status, applies only to
>         HTTP/1.1 requests, and not to requests with any other HTTP-
>         version value.

So, teach the clients to not send the Expect header and/or use HTTP/1.0.
Apache does not send the header without the client "Expect"ing it.

HTH, nd

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message