Content-Length header with HEAD requests?

by

To me it looks like the HTTP 1.1 RFC is pretty specific:

The Content-Length
entity-header field indicates the size of the entity-body, in decimal
number of OCTETs, sent to the recipient or, in the case of the HEAD
method, the size of the entity-body that would have been sent had
the request been a GET.

More Related Contents:

  1. Detecting the character encoding of an HTTP POST request
  2. Is REST DELETE really idempotent?
  3. Is an entity body allowed for an HTTP DELETE request?
  4. Are HTTP headers case-sensitive?
  5. What’s the difference between Cache-Control: max-age=0 and no-cache?
  6. Uses of content-disposition in an HTTP response header
  7. ‘Refresh’ HTTP header
  8. Which status code should I use for failed validations or invalid duplicates?
  9. Difference between Pragma and Cache-Control headers?
  10. What are all the possible values for HTTP “Content-Type” header?
  11. Ideal HTTP cache control headers for different types of resources
  12. Remove http referer
  13. Why does my web server software disallow PUT and DELETE requests?
  14. Proper REST response for empty table?
  15. Which HTTP methods match up to which CRUD methods?
  16. Why is Cache-Control attribute sent in request header (client to server)?
  17. How to forward headers on HTTP redirect
  18. What is the difference between HTTP and REST?
  19. Doing a HTTP PUT from a browser
  20. What is q=0.5 in Accept* HTTP headers?
  21. Standard for adding multiple values of a single HTTP Header to a request or response
  22. What is a full specification of X-Forwarded-Proto HTTP header?
  23. Setting HTTP headers
  24. Payloads of HTTP Request Methods
  25. What HTTP response headers are required
  26. what characters are allowed in HTTP header values?
  27. What does HTTP/1.1 302 mean exactly?
  28. HTTP Cache Control max-age, must-revalidate
  29. Should I use PATCH or PUT in my REST API?
  30. S3: How to do a partial read / seek without downloading the complete file?

Leave a Comment