You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am currently using this (awesome) plugin with HLS protected streams and facing an issue.
The source URL set in Clappr options authenticate the user, based in several factors, and redirects to a new HLS manifest URL with a token attached (to the query string) - which finally reponds with the chunklist - and Clappr perform new requests every few seconds to this final URL (with the token).
However, when I click the Chromecast icon, the initial URL is sent to Chromecast (without the token) and it pings that URL every few seconds, following the redirect to get the chunklist and obtaining a new token every time.
I am not sure it is an error by this plugin or in Chromecast's procedures internally. It could do as Clappr (Hls.js) does and check for manifest updates on the URL it was forwarded to (with the token). But certainly this problem could be prevented by this plugin, passing to the Chromecast device the URL with the token (where the manifest redirects to).
Anyway, passing the final URL of the manifest (with the token) would be even more useful since "environment" information available to Clappr player and this plugin (like the the Origin header, HTTP Referer header, the cookies passed along the request to the initial manifest URL, etc) are not available otherwise.
The text was updated successfully, but these errors were encountered:
Hello, I am currently using this (awesome) plugin with HLS protected streams and facing an issue.
The
source
URL set in Clappr options authenticate the user, based in several factors, and redirects to a new HLS manifest URL with a token attached (to the query string) - which finally reponds with the chunklist - and Clappr perform new requests every few seconds to this final URL (with the token).However, when I click the Chromecast icon, the initial URL is sent to Chromecast (without the token) and it pings that URL every few seconds, following the redirect to get the chunklist and obtaining a new token every time.
I am not sure it is an error by this plugin or in Chromecast's procedures internally. It could do as Clappr (Hls.js) does and check for manifest updates on the URL it was forwarded to (with the token). But certainly this problem could be prevented by this plugin, passing to the Chromecast device the URL with the token (where the manifest redirects to).
Anyway, passing the final URL of the manifest (with the token) would be even more useful since "environment" information available to Clappr player and this plugin (like the the Origin header, HTTP Referer header, the cookies passed along the request to the initial manifest URL, etc) are not available otherwise.
The text was updated successfully, but these errors were encountered: