Re: Fwd: HTTP redirect for HTTP Adaptive Streaming (HAS) in CDN use cases

Thanks Julian.

In that case, for Example 2:
Would you say that the base URI for /vod/movie/master.m3u8 is resolved by
section 5.1.3 from the retrieval URI?
In that case the base URI for /vod/movie/master.m3u8 is
https://edge1.dcdn.example.net/vod/movie/master.m3u8.
Since the relative reference 1800K/1800_complete.m3u8 is encapsulated
within master.m3u8, it should be resolved according to section 5.1.2 and
should therefore be
https://edge1.dcdn.example.net/vod/movie/1800K/1800_complete.m3u8

So, example 2 behaves well, according to this interpretation.

For example 3:
Following your input, master.m3u8 IS NOT encapsulated in the HTML (the URI
is), and therefore its base URI should be computed by section 5.1.3 from
the retrieval URI, as in Example 2.
That would lead to the same result that the
vod/movie/1800K/1800_complete.m3u8 base URI is at the edge cache.
https://edge1.dcdn.example.net/vod/movie/1800K/1800_complete.m3u8

Is this the correct interpretation ?
If so, then all these examples lead to the same conclusion that the client
should be 'sticky'.

Thanks,
Ori


On Sun, Nov 4, 2018 at 12:12 PM Julian Reschke <julian.reschke@gmx.de>
wrote:

> On 2018-11-03 14:01, Ori Finkelman wrote:
> >
> > [Resending as I have sent to the wrong list]
> >
> >
> > Hello ,
> > ...
>
> Interesting, but...:
>
> > 6.2.  Example 2: Relative reference in an Encapsulating Entity
> >
> >    Let us take the same example but instead of the player being passed
> >    an absolute URI, let us assume the URI is relative and embedded
> >    within another entity (e.g., within a top-level HTML page
> >    https://video.cdn.example.com/index.html) In that case /vod/movie/
> >    master.m3u8 (the encapsulating entity of 1800K/1800_complete.m3u8) is
> >    itself encapsulated (in /index.html) and Section 5.1.2 does apply
> >    this time, and the base URI of /vod/movie/master.m3u8 depends on the
> >    base URI of /index.html
>
> No.
>
> The entity for </vod/movie/master.m3u8> is *not* embedded in the HTML.
> It's *URI* is. This is very different.
>
> Unless I'm missing something, this is simply a misinterpretation of the
> terminology.
>
> Best regards, Julian
>


-- 

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