- From: Ori Finkelman <orif@qwilt.com>
- Date: Tue, 13 Nov 2018 15:02:43 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: daniel@haxx.se, ietf-http-wg@w3.org
- Message-ID: <CAMb9nTub=Z1C6QngL=vazDZv+35Hp5Dhu7oyHZ_=dKGhdnk4ew@mail.gmail.com>
Hi Julian, Ideally I would seek clarifications for both the meaning of a redirect and for the base URI establishment (the confusion about embedding resource). But, while the embedding issue I think we can explain well enough using the inputs we got from you and Patrick, the redirect IMHO is still confusing due to the "the client ought to continue to use the effective request URI for future requests" Clarifying both issues would make it very clear that anything else is not conforming with the RFC and would help conclude the debates in the player development community. Thanks, Ori On Tue, Nov 13, 2018 at 2:51 PM Julian Reschke <julian.reschke@gmx.de> wrote: > On 2018-11-13 12:32, Ori Finkelman wrote: > > Hi Daniel, > > Indeed the base URI is not mentioned, > > https://tools.ietf.org/html/rfc7231#section-6.4.3 refers to the > > effective request URI. > > So, what is the effective request URI ? from this phrasing my > > understanding is that it is the original URI before redirection (as the > > context is that the the redirection might be altered). > > > > If it's the original URI, then this is, IMHO, what is causing > > confusion, as some reads it as "you should not use the redirected URL > > for anything other than the local retrieval of that specific request". > > This, is in contradiction with > > https://tools.ietf.org/html/rfc3986#section-5.1.3, but the confusion is > > still there. > > > > I am trying to have a clarification so I can go back with that to the > > video players community and promote fixes to align with the correct > > behavior. > > > > What I would suggest as phrasing (without taking a stand where to put > it): > > "Clients automatically following redirect must note that the redirected > > request is a separate request and as such, the URI of the retrieved > > object after redirection is the redirection URI" > > > > Thanks, > > Ori > > ...once again: does this fix the issue that you reported? Wasn't that > really about the confusion about "embedding a resource"? > > Best regards, Julian > -- *Ori Finkelman*Qwilt | Work: +972-72-2221647 | Mobile: +972-52-3832189 | orif@qwilt.com
Received on Tuesday, 13 November 2018 13:03:48 UTC