- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sun, 4 Nov 2018 11:12:44 +0100
- To: Ori Finkelman <orif@qwilt.com>, ietf-http-wg@w3.org, ggie@ietf.org, "Begen, Ali (Contractor)" <Ali_Begen@comcast.com>
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
Received on Sunday, 4 November 2018 10:13:25 UTC