> Am 10.04.2019 um 15:57 schrieb Julian Reschke <julian.resc...@gmx.de>: > > On 10.04.2019 14:53, Plüm, Rüdiger, Vodafone Group wrote: >> ... >> Not sure about this. I guess with TE each hop could be different in what it >> accepts >> and generates. This is different from CE. As far as I understand the >> accept-encoding header >> is only for CE not for TE. >> ... > > Right (that would be "TE"). > > That aside, maybe it's time to remind that HTTP/2 doesn't have transfer > codings? You mean, it does not have "chunked". > Best regards, Julian
- Re: keep-alive and vary in 304 responses Roy T. Fielding
- Re: keep-alive and vary in 304 resp... Stefan Eissing
- Re: keep-alive and vary in 304 ... Yann Ylavic
- AW: keep-alive and vary in ... Plüm , Rüdiger , Vodafone Group
- Re: keep-alive and vary... Stefan Eissing
- Re: keep-alive and vary... Yann Ylavic
- AW: keep-alive and... Plüm , Rüdiger , Vodafone Group
- Re: keep-alive... Stefan Eissing
- AW: keep-alive... Plüm , Rüdiger , Vodafone Group
- Re: AW: keep-a... Julian Reschke
- Re: keep-alive... Stefan Eissing
- Re: keep-alive... Julian Reschke
- Re: keep-alive... Stefan Eissing
- Re: keep-alive and vary in ... Julian Reschke
- AW: keep-alive and vary in 304 ... Plüm , Rüdiger , Vodafone Group
- Re: keep-alive and vary in ... Stefan Eissing
- Re: keep-alive and vary in 304 ... Roy T. Fielding
- HTTP Protocol workshop notes William A Rowe Jr
- Re: keep-alive and vary in 304 responses Mario Brandt
- Re: keep-alive and vary in 304 resp... Julian Reschke
- Re: keep-alive and vary in 304 ... Yann Ylavic