What is q=0.5 in Accept* HTTP headers?

by

This is called a relative quality factor. It specifies what language the user would prefer, on a scale of 0 to 1, as can be seen from the HTTP/1.1 Specification, ยง14.4:

Each language-range MAY be given an associated quality value which represents an estimate of the user’s preference for the languages specified by that range. The quality value defaults to “q=1”. For example,

  Accept-Language: da, en-gb;q=0.8, en;q=0.7

would mean: “I prefer Danish, but will accept British English and other types of English.”

More Related Contents:

  1. application/x-www-form-urlencoded or multipart/form-data?
  2. Are HTTP headers case-sensitive?
  3. Do I need Content-Type: application/octet-stream for file download?
  4. Maximum on HTTP header values?
  5. Custom HTTP headers : naming conventions
  6. What’s the difference between Cache-Control: max-age=0 and no-cache?
  7. Difference between Pragma and Cache-Control headers?
  8. Is there a practical HTTP Header length limit?
  9. Detecting the character encoding of an HTTP POST request
  10. HTTP Range header
  11. How can I get the clients IP address from HTTP headers?
  12. Content-Length header with HEAD requests?
  13. Why is Cache-Control attribute sent in request header (client to server)?
  14. How to forward headers on HTTP redirect
  15. Difference between Content-Range and Range headers?
  16. How does “304 Not Modified” work exactly?
  17. How big can a user agent string get?
  18. What is Cache-Control: private?
  19. Standard for adding multiple values of a single HTTP Header to a request or response
  20. How can I find out whether a server supports the Range header?
  21. Setting HTTP headers
  22. what characters are allowed in HTTP header values?
  23. Does the HTTP Protocol support multiple content types in response headers?
  24. What is the http-header “X-XSS-Protection”?
  25. What is HTTP “Host” header?
  26. How to evaluate http response codes from bash/shell script?
  27. Is the Content-Length header required for a HTTP/1.0 response?
  28. Is REST DELETE really idempotent?
  29. Avoid caching of the http responses
  30. Keep-alive header clarification

Leave a Comment