You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vast majority of real world traffic uses lowercase, but some does
not, and it is technically case insensitive, so lets support it.
This also adds 'binary', yet another common content-encoding mistake
that seems to mean "there's no encoding here".
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ The supported codecs are:
12
12
* Brotli
13
13
* Zstandard
14
14
15
-
The 'identity', 'amz-1.0', 'none', 'text'and 'utf-8' encodings (no-op encodings) are also supported, passed through with no en/decoding at all. Only 'identity' is standard, but the others are all in common use regardless.
15
+
All encoding names are case-insensitive (although lowercase is generally standard). The 'identity', 'amz-1.0', 'none', 'text', 'binary' and 'utf-8' encodings (no-op encodings) are all supported as no-op encodings, passed through with no en/decoding at all. Only 'identity' is standard, but the others are all in common use regardless.
16
16
17
17
Found a codec used in real-world HTTP that isn't supported? Open an issue!
0 commit comments