- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 13 Nov 2018 13:51:48 +0100
- To: Ori Finkelman <orif@qwilt.com>, daniel@haxx.se
- Cc: ietf-http-wg@w3.org
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
Received on Tuesday, 13 November 2018 12:52:21 UTC