Relative URIs with absolute paths are not resolved correctly

[tedjp]

A relative URI that starts with a / is not parsed correctly. It should replace the path component of its context, but in dash.js it is appended to the directory component of the context URL.

These relative URIs are specified in RFC 3986 as "path-absolute".

For example serving the MPD below from /MPDs/baseurl.mpd results in dash.js requesting /MPDs//path/at/root/video_900000bps.mp4 when it should be requesting /path/at/root/video_900000bps.mp4.

<?xml version="1.0"?>
<MPD xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns="urn:mpeg:dash:schema:mpd:2011"
  xsi:schemaLocation="urn:mpeg:dash:schema:mpd:2011 DASH-MPD.xsd"
  type="static"
  minBufferTime="PT2S"
  profiles="urn:mpeg:dash:profile:isoff-live:2011"
  mediaPresentationDuration="PT234S">
  <Period>
    <BaseURL>/path/at/root/</BaseURL>
    <AdaptationSet mimeType="video/mp4" segmentAlignment="true" startWithSAP="1">
      <SegmentTemplate duration="2" startNumber="1"
         media="video_$Number$_$Bandwidth$bps.mp4"
         initialization="video_$Bandwidth$bps.mp4"/>
      <Representation id="v0" codecs="avc1.4d401e"
         width="720" height="576" bandwidth="900000"/>
    </AdaptationSet>
  </Period>
</MPD>

A similar test can be constructed with BaseURL elements in nested scope, each with an absolute path.

[TalLevAmi]

It seems that this issue was re-introduced by 2328620
The support for prepending the origin's host and protocol to the path-absolute urls has been removed.

[davemevans]

Confirmed.

[davemevans]

@TalLevAmi I believe davemevans@c7efeb6 should address this. Please could you try applying that and report back? If so, I'll create a PR.

[TalLevAmi]

@bbcrddave Confirmed it works. Thanks for the quick response!