On Thu, Aug 1, 2019 at 5:46 PM Kari Hurtta <hurtta-ietf@elmme-mailer.org> wrote: > So if SETTINGS frame changes meaning of PRIORITY data which is already > sent, that causes that server will interpreted it different than > what http client intended. > > There may be also Stream Dependency field on HEADERS frame. > > And also PRIORITY frame may be send before HEADERS frame when stream > is on idle state. > > So that repurpose will not work. > > Any client that is taking the chance to make a semantic change to the frames it is sending would be foolish to not wait on an affirmative signal from the server. RFC 7540 Section 5.5. calls specific attention to such a repurposing: > Extensions that could change the semantics of existing protocol components MUST be negotiated before being used. For example, an extension that changes the layout of the HEADERS frame cannot be used until the peer has given a positive signal that this is acceptable. Lucas
Received on Thursday, 1 August 2019 17:47:56 UTC