Skip to content

Commit

Permalink
Update files/en-us/web/http/headers/accept-encoding/index.md
Browse files Browse the repository at this point in the history
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
  • Loading branch information
bsmth and hamishwillee authored Nov 13, 2024
1 parent 0d07450 commit 91277bc
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion files/en-us/web/http/headers/accept-encoding/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ browser-compat: http.headers.Accept-Encoding

The HTTP **`Accept-Encoding`** {{glossary("request header", "request")}} and {{glossary("response header")}} indicates the content encoding (usually a compression algorithm) that the recipient can understand.
In requests, the server uses [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation) to select one of the encoding proposals from the client and informs the client of that choice with the {{HTTPHeader("Content-Encoding")}} response header.
In responses, it provides information about which encodings are preferred in the content of a subsequent request to the same resource.
In responses, it provides information about which content encodings the server can understand in messages to the requested resource, so that the encoding can be used in subsequent requests to the resource. For example, this might be sent in the response to a `PUT` request to a resource that used an unsupported encoding.

Even if both the client and the server support the same compression algorithms, the server may choose not to compress the body of a response if the `identity` value is also acceptable.
This happens in two common cases:
Expand Down

0 comments on commit 91277bc

Please sign in to comment.