New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Live streaming is stuck, get lots of 403 (forbidden) #3786
Comments
We'll the URI's in the console output seem to have similar query parameters to the once in the playlist. I'd guess it's the extremely short validity of your signed URI's that's the problem. |
I've checked the query parameters that are inconsistent:
The sorted is different and some sign are encoded. |
Those both parse to the same output except for the order. Ordering of query parameters should not matter as it's quite common for caching/CDN infrastructure to sort query parameters to increase hit ratios. No RFC requires parameter order to be preserved and I've never encountered a system that needed it. original parsed:
403 parsed:
Have you checked one of those URLs directly after they 403? |
Sure.
Yes, the server side isn't own, so I just request again and get same response(403). I have some provider give me the live streaming URL(m3u8), one of provider URL that doesn't have any query parameters, that is no any issue, but the others have query parameters their URLs will cause 403. This issue can't reproduce on v0.14.17. The PR is just using origin URL and doesn't get 403. |
What version of Hls.js are you using?
v1.0.0 and v1.0.1
What browser and OS (including versions) are you using?
Chrome 89.0.4389.114, Windows 10 Pro
Test stream:
None. Sorry, our streaming URL will expire when get the URL after 30 second and not public.
Configuration:
Default
Checklist
Steps to reproduce
Expected behavior
No network error and doesn't stuck.
Actual behavior
Get lots of 403 (forbidden) that will cause the streaming stuck
Console output
The text was updated successfully, but these errors were encountered: