[GitHub] [httpcomponents-client] michael-o commented on pull request #250: Avoid updating Content-Length header in a 304 response.

[GitBox <gi...@apache.org>]

michael-o commented on pull request #250:
URL: https://github.com/apache/httpcomponents-client/pull/250#issuecomment-675405532


   Both headers seem to be pointless, RFC says:
   
   ```
      The server generating a 304 response MUST generate any of the
      following header fields that would have been sent in a 200 (OK)
      response to the same request: Cache-Control, Content-Location, Date,
      ETag, Expires, and Vary.
   
      Since the goal of a 304 response is to minimize information transfer
      when the recipient already has one or more cached representations, a
      sender SHOULD NOT generate representation metadata other than the
      above listed fields unless said metadata exists for the purpose of
      guiding cache updates (e.g., Last-Modified might be useful if the
      response does not have an ETag field).
   ```


----------------------------------------------------------------
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org