d2r opened a new issue #2543:
URL: https://github.com/apache/trafficserver/issues/2543


   The config [defaults](proxy.config.http.send_100_continue_response) to `0`, 
which is incongruent with the proposed standard [RFC7231 
5.1.1](https://tools.ietf.org/html/rfc7231#section-5.1.1).
   
   ```
   An origin server MUST, upon receiving an HTTP/1.1 (or later)
   request-line and a complete header section that contains a
   100-continue expectation and indicates a request message body will
   follow, either send an immediate response with a final status code,
   if that status can be determined by examining just the request-line
   and header fields, or send an immediate 100 (Continue) response to
   encourage the client to send the request's message body.  The origin
   server MUST NOT wait for the message body before sending the 100
   (Continue) response.
   
   A proxy MUST, upon receiving an HTTP/1.1 (or later) request-line and
   a complete header section that contains a 100-continue expectation
   and indicates a request message body will follow, either send an
   immediate response with a final status code, if that status can be
   determined by examining just the request-line and header fields, or
   begin forwarding the request toward the origin server by sending a
   ```
   
   Clients are seen already using header. Should we consider proactively 
switching the default in some future release?
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to