- From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Date: Sun, 13 Nov 2016 18:40:43 +0200 (EET)
- To: HTTP working group mailing list <ietf-http-wg@w3.org>
- CC: Alex Rousskov <rousskov@measurement-factory.com>, Kazuho Oku <kazuhooku@gmail.com>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
> HTTP headers are end-to-end by default. Therefore a request header for > negotiating the use of 103 would go through an intermediary incapable > of handling 1xx correctly. We might consider designating the header > used for negotiation as a hop-by-hop header, but I'd be scared of > using a new token to the connection header (for interoperability > issues). It is also possible to Connection: -header implementation is broken. So if 1xx is broken, it does not help use Connection: for to indicate hop-by-hop header if this is not honored either. Seems likely that both little used featured are broken on same implementation. / Kari Hurtta
Received on Sunday, 13 November 2016 16:41:19 UTC