Hi folks,

I've recently checked on baseURL failover for DASH manifests that was added with ExoPlayer version 2.15.0 and found an asset not working as expected.

I cannot share the content url however it should be easily reproducible with the following snippet:

<Period>
    <BaseURL>//anotherhost.com/some/url/1</BaseURL>
    <BaseURL>//anotherhost.com/some/url/2</BaseURL>
    ...
</Period>

I'm not sure if those relative network-path are considered to be valid and/or supported, so thought I'll bring this to your attention.

From what I can tell from my observation is, that in such a case the serviceLocation is mapped to the manifests base Url, and down the line being added to the exclusion list (after the first BaseUrl failed), thus excluding all base urls with the same serviceLocation.

Happy to hear your thoughts.