allow HTTP request headers to be customized for each video in queue
* POST data sent in requests to "/play" and "/queue" API endpoints:
- now recognizes the keys:
* req-header
* drm-header
- ex:
req-header: Referer: http://example.com/videos.html
req-header: Origin: http://example.com
drm-header: Authorization: Bearer <TOKEN>
* Intents
- which are:
* used to start StartNetworkingServiceActivity
* and forwarded to NetworkingService
- can now include the extras:
* reqHeader
* drmHeader
- which can be data type:
* String[]
* String
- and each String is formatted:
* "header-name: header-value"
* POST data sent in requests to "/start-activity" API endpoint:
- can configure these Intent extras
* extra-reqHeader
* extra-drmHeader
- ex:
extra-reqHeader: Referer: http://example.com/videos.html
extra-reqHeader: Origin: http://example.com
extra-drmHeader: Authorization: Bearer <TOKEN>
notes:
* the ability to configure "referer" is now redundant
- keys:
* POST data: referer
* Intent extra: referUrl
- this feature is legacy, and kept to avoid breaking userspace
* DRM headers are only used when
both DRM scheme and DRM license server URL are provided
* ExoAirPlayer is configured with a default "User-Agent"
- which impersonates a recent version of Chrome for Windows desktop
- custom request headers can override this default value
