Re: HTTP redirect section draft-ietf-httpbis-bcp56bis-08

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




On Tue, Nov 13, 2018 at 12:33 PM Daniel Stenberg <daniel@haxx.se> wrote:

> On Tue, 13 Nov 2018, Ori Finkelman wrote:
>
> > > ...Since the redirection might be altered on occasion, the client
> ought to
> > > continue to use the effective request URI for future requests.
> >
> > This can be wrongly interpreted as "the redirect does not change the base
> > URI of the object".
>
> Can you clarify how you can come to that conclusion? Or perhaps suggest an
> alternative phrasing that would've helped to avoid that mistake?
>
> Base URI/URL isn't even used as a term in the document (barring a
> reference in
> the appendix to changes from 2616).
>
> --
>
>   / daniel.haxx.se
>
>

-- 

*Ori Finkelman*Qwilt | Work: +972-72-2221647 | Mobile: +972-52-3832189 |
orif@qwilt.com