W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2022

Re: Deployment of draft-ietf-httpbis-cice (Client-Initiated Content-Encoding)

From: Wenbo Zhu <wenboz@google.com>
Date: Mon, 7 Nov 2022 10:56:04 -0800
Message-ID: <CAD3-0rM3U4kyqnMmJnHLAzi9=RYzGz2pVBKr5hXRH57+Lt1-3A@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: ietf-http-wg@w3.org
On Wed, Nov 2, 2022 at 11:37 AM Julian Reschke <julian.reschke@gmx.de>
wrote:

> On 02.11.2022 18:45, Wenbo Zhu wrote:
> > ...
>
> I still don't get what the issue is.
>
> Could you post a complete message exchange that illustrates the
> potential problem?
>
Client sends a POST with C-T: Foo; C-E: br
Server doesn't yet support br uncompression, and will now return 415 (based
on this spec), instead of something like 400
Server also needs to set A-E: gzip. However, based on the rules known to
the server, Foo is not a compressible (with gzip at least) media type

The question is whether A-E: identity is preferred.




> Best regards, Julian
>
>
Received on Monday, 7 November 2022 18:56:29 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 28 January 2023 21:29:46 UTC