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

WebRTC offer requires form-data #215

Closed
timurkhakhalev opened this issue Sep 11, 2022 · 4 comments · Fixed by #216
Closed

WebRTC offer requires form-data #215

timurkhakhalev opened this issue Sep 11, 2022 · 4 comments · Fixed by #216

Comments

@timurkhakhalev
Copy link
Contributor

Hi! Please clarify in your API Documentation for WebRTC that your server is waiting for form-data info which needs to include: 'data': 'base64 encoded sdp offer'.
Its takes me very much hours to understand what I do wrong because I got error "SetRemoteDescription called with no ice-ufrag" every time because I used simple body json data to pass SDP offer.

@allenporter
Copy link
Collaborator

It would be great if you sent an update to the documentation!

@allenporter
Copy link
Collaborator

https://github.com/deepch/RTSPtoWeb/blob/master/docs/api.md

The request is an HTTP POST with a parameter data that is a base64 encoded SDP offer (e.g. v=0...) from a WebRTC client.

@timurkhakhalev
Copy link
Contributor Author

timurkhakhalev commented Sep 11, 2022

https://github.com/deepch/RTSPtoWeb/blob/master/docs/api.md

The request is an HTTP POST with a parameter data that is a base64 encoded SDP offer (e.g. v=0...) from a WebRTC client.

Yeah I mean it would be great if you clarify that it must be FormData

@allenporter
Copy link
Collaborator

Yeah I'm suggesting your contribution would be welcome to that page. (It seems perfectly clear to me, so an outside perspective could do a better job at clarifying what's missing.) Send an edit!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants