Relative BaseURL at MPD level only do not resolve correctly

Created by: davemevans

Say you serve the following manifest from http://www.example.com/dir/

<MPD>
<BaseURL>../<BaseURL>

...
</MPD>

The BaseURL should resolve to http://www.example.com/

There's a bug in the Base URL handling which assumes that MPD@BaseURL entries will always be absolute (or non-existent, which works fine). If these entries are relative, they fail to resolve as specified.

The workaround is to ensure MPD@BaseURL entries are absolute.

This problem only affects entries at the MPD level - all other levels work correctly.

I hope to fix this tomorrow (Tuesday 12th) in time for 2.1.0 release.