- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 24 Mar 2015 14:25:48 +0100
- To: Mark Nottingham <mnot@mnot.net>, Patrick McManus <mcmanus@ducksong.com>
- CC: Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 2015-03-22 17:32, Mark Nottingham wrote: > So, I think we could solve Patrick’s issue by saying: > > """ > An ALTSVC frame on a client-initiated stream containing non-empty "Origin" information is invalid and must be ignored. Likewise, an ALTSVC frame on stream 0 with empty (length 0) "Origin" information is invalid and must be ignored. > """ > > to: > > """ > An ALTSVC frame on stream 0 with empty (length 0) "Origin" information is invalid and must be ignored. An ALTSVC frame on a stream other than stream 0 containing non-empty "Origin" information is invalid and must be ignored. > """ > > WRT Julian's issue, I think we could address this by changing > > """ > An ALTSVC frame from a server to a client on a client-initiated stream indicates that the conveyed alternative service is associated with the origin of that stream. > """ > > to: > > """ > An ALTSVC frame from a server to a client on a stream other than stream 0 indicates that the conveyed alternative service is associated with the origin of that stream. > """ > > Both of these assume that we want to allow ALTSVC on a pushed stream. > > Discuss... SGTM.
Received on Tuesday, 24 March 2015 13:26:25 UTC