We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is not (yet) regulated in the WHEP protocol but from a general HTTP endpoint perspective it is good if the endpoint handles OPTIONS request, e.g.
curl -X OPTIONS -v "https://srtwhep.lab.sto.eyevinn.technology:8443/channel"
Expected to return the following headers and status code 204, e.g:
204
< HTTP/1.1 204 No Content < Server: nginx/1.14.0 (Ubuntu) < Date: Mon, 21 Aug 2023 07:34:44 GMT < Connection: keep-alive < vary: Origin, Access-Control-Request-Headers < access-control-allow-origin: * < access-control-expose-headers: Location, Accept, Allow, Accept-POST < access-control-allow-methods: POST, GET, OPTIONS, PATCH, PUT < accept-post: application/sdp <
The text was updated successfully, but these errors were encountered:
Wkkkkk
No branches or pull requests
This is not (yet) regulated in the WHEP protocol but from a general HTTP endpoint perspective it is good if the endpoint handles OPTIONS request, e.g.
Expected to return the following headers and status code
204
, e.g:The text was updated successfully, but these errors were encountered: