-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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 source bad Content-Type -- got 'application/sdp; charset=utf-8' #3273
Comments
Suggested changes:
|
Accept (optional) charsets Close: bluenviron#3273
Accept (optional) charsets Close: bluenviron#3273
#3274 helps but unfortunately it stiil does not work with VDO.ninja. The next error is:
It certainly necessitates another issue, but I'm unsure if it is an error of mediamtx or VDO.Ninja. |
Accept (optional) charsets Close: bluenviron#3273
Thanks for reporting the new WHIP/WHEP feature of vdo.ninja. The second blocking issue is fixed by #3277 |
This issue is mentioned in release v1.8.0 🚀 |
Thank you for your responsiveness and your great work on mediamtx. |
This issue is being locked automatically because it has been closed for more than 6 months. |
Which version are you using?
v1.7.0
Which operating system are you using?
Describe the issue
I'm currently trying mediamtx, and I wanted to try the WHEP ingest function.
To do so, I used VDO.Ninja service, that is known to work very well as a WebRTC streaming service.
Unfortunately, this service responds to WHEP resquests with the following Content-Type header:
application/sdp; charset=utf-8
.Mediamtx does not like it, as it expects exactly
application/sdp
as Content-Type, and the content is not retrieved.Describe how to replicate the issue
Add this snippet to the mediamtx configuration:
After launching the stream using VDO.Ninja -- Host a VDO.Ninja stream as a WHEP source with the WHEP token
p827NUkn
, and starting the mediamtx container, it fails with the following message:Did you attach the server logs?
Did you attach a network dump?
no
why? the network traffic is encrypted with TLS, therefore, we cannot observe the headers/data transmitted.
Others
I might create a PR if I have the time and if I figure out a solution to this issue.
The text was updated successfully, but these errors were encountered: