-
Notifications
You must be signed in to change notification settings - Fork 345
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
Fix complex Content-Type for image/jpeg #278
Comments
Of note in the mpeg producer line 36 is:
So the charset is breaking that I assume. Considering charset= blah is a valid value within content type seems like this should be modified to allow for that. |
I think making the if statement
Would fix it. |
Stupid content type. JPEG can't have any charset setting. It's a binary format. Will be fixed in next release. |
Thanks. |
AlexxIT
added a commit
that referenced
this issue
Jul 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have an old hikvision cube (2432) I have been trying to get to work correctly with go2rtc, but I am having issues with the snapshots. Currently the camera is providing 2 streams (20481536 H264 audio and video, and 704480 H264 audio and video). I have two streams setup, one for main and one for the sub. As follows
I tried adding the JPEG as an HTTP which can be found at - http://user:password@IP:554/Streaming/Channels/101/picture ... the 102 channel doesn't support JPEG.
The issue is that when I do that I get the following error.
When I manually look at the headers in chrome, I noticed that the Content-Type inculdes the the charset.... "image/jpeg; charset="UTF-8""
Which I am guessing is causing the issue.
Is there a way around this? I was thinking about setting up a nginx proxy to strip the headers, but that just seemed crazy....
The text was updated successfully, but these errors were encountered: