-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
PROTOCOL: JS API FETCH STREAM for flv.js #798
Comments
It is a standard HTTP GET, both chunked or non-chunked are acceptable.
|
Just need to add the header 'Access-Control-Allow-Origin' to the output, you can try playing with flv.js.
|
Tested on version 3.0.18, it also needs to be added in the Header. The output of the Chrome test is as follows:
|
Hello, I tried using flv.js to play http flv, but I still encountered the error message "Fetch API cannot load http://.../live/livestream.flv. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://...' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled." How can I resolve this issue? Thank you.
|
You can temporarily use a proxy. Refer to #722 @hman190
|
Just enable crossdomain, refer to the configuration.
|
I enabled crossdomain but it didn't work. I'll try again later.
|
Make sure to open it in http_server, and if there are any issues, please provide feedback.
|
Now it's good.
|
Great~ |
hi winlinvip
|
SRS3 can support it, but it has not been released.
|
I compiled using the latest source code, but still have this issue.
|
When using flv.js to play FLV, there is a cross-origin issue. To solve this, add
|
I will supplement the issue of cross-domain once again:
|
Reference: #691 (comment)
It seems that there is a new JS API that supports streaming reading with GET. However, it is unclear whether SRS needs to provide support for this or if standard HTTP GET is sufficient. Therefore, creating this bug to track it.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: