diff options
| author | Patrick Monnerat <patrick@monnerat.net> | 2017-11-05 15:09:48 +0100 |
|---|---|---|
| committer | Patrick Monnerat <patrick@monnerat.net> | 2017-11-05 15:09:48 +0100 |
| commit | dbcced8e32b50c068ac297106f0502ee200a1ebd (patch) | |
| tree | 0fa1ce28f33ab968792e21264e9a9318807d9f9b /docs/TODO | |
| parent | 462f3cac34c09b9c28b449258e71dc37171dc604 (diff) | |
HTTP: support multiple Content-Encodings
This is implemented as an output streaming stack of unencoders, the last
calling the client write procedure.
New test 230 checks this feature.
Bug: https://github.com/curl/curl/pull/2002
Reported-By: Daniel Bankhead
Diffstat (limited to 'docs/TODO')
| -rw-r--r-- | docs/TODO | 7 |
1 files changed, 0 insertions, 7 deletions
@@ -67,7 +67,6 @@ 5.7 Brotli compression 5.8 QUIC 5.9 Leave secure cookies alone - 5.10 Support Multiple Content-Encodings 6. TELNET 6.1 ditch stdin @@ -538,12 +537,6 @@ This is not detailed in any FTP specification. https://tools.ietf.org/html/draft-ietf-httpbis-cookie-alone-01 -5.10 Support Multiple Content-Encodings - - RFC 7231 Section 3.1.2.2 allows multiple encodings for a single request. Using - this may result in lower bandwidth and promotes a more resource-friendly web. - Currently, Chrome and Firefox support multiple encodings. - 6. TELNET |