Skip to content
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

Handle OPTIONS request #47

Closed
birme opened this issue Aug 21, 2023 · 0 comments
Closed

Handle OPTIONS request #47

birme opened this issue Aug 21, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@birme
Copy link
Contributor

birme commented Aug 21, 2023

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:

< 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
< 
@Wkkkkk Wkkkkk self-assigned this Aug 21, 2023
@Wkkkkk Wkkkkk added the enhancement New feature or request label Aug 21, 2023
@Wkkkkk Wkkkkk mentioned this issue Aug 21, 2023
@Wkkkkk Wkkkkk closed this as completed Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants