manifest domain: https://mozilla.seanfeng.dev

resource domain: https://mozilla.seanfeng.dev

Both manifest and resources are same origin

manifest domain: https://hls.seanfeng.dev

resource domain: https://hls.seanfeng.dev

Both manifest and resources are cross origin

manifest domain: https://mozilla.seanfeng.dev

resource domain: https://hls.seanfeng.dev

manifest is same origin, and it contains resources that are cross-origin

manifest domain: https://mozilla.seanfeng.dev

resource domain: https://mozilla.seanfeng.dev -> https://hls.seanfeng.dev

manifest is same origin, and it contains resources that are same-origin but will be redirected to a cross-origin

manifest domain: https://mozilla.seanfeng.dev

resource domain: https://mozilla.seanfeng.dev -> https://hls.seanfeng.dev -> https://mozilla.seanfeng.dev

manifest is same origin, and it contains resources that are same-origin but will be redirected to a cross-origin, and then redirect back to same origin

manifest domain: https://hls.seanfeng.dev

resource domain: https://hls2.seanfeng.dev

manifest is cross-origin, resource is also cross-origin

manifest domain: https://mozilla.seanfeng.dev(android-allow-cross-domain-redirect: 0)

resource domain: https://mozilla.seanfeng.dev -> https://hls.seanfeng.dev

manifest is same origin, and it contains resources that are same-origin but will be redirected to a cross-origin. And the manifest response contains the 'android-allow-cross-domain-redirect' header