GNOME Bugzilla – Bug 793110
rtspconnection: No Content-Type header in HTTP POST requests for RTSP tunnelling
Last modified: 2018-02-08 16:29:10 UTC
Created attachment 367781 [details] [review] Add the correct content-type to the HTTP POST request When the GstRTSPConnection class sends a RTSP over HTTP tunnelling request, the HTTP Content-Type header is missing from the HTTP POST request. This isn't a problem with most servers, but I have access to a server that rejects the request. Relevant specifications: RFC 1945: Any HTTP/1.0 message containing an entity body should include a Content-Type header field defining the media type of that body. Apple Dispatch 28: QuickTime Streaming uses the "application/x-rtsp-tunnelled" MIME type in both the Content-Type and Accept headers. This reflects the data type that is expected and delivered by the client and server.
Thanks for the patch! Next time it would be great if you could submit the patch in "git format-patch" format with author/data/commit message :) commit 9e77d9cacf5960c54bb0a26688208d898b380ea0 Author: Sebastian Cote <sebas642@yahoo.ca> Date: Fri Feb 2 00:00:23 2018 +0000 rtspconnection: also add Content-Type to HTTP POST request when tunnelling When the GstRTSPConnection class sends a RTSP over HTTP tunnelling request, the HTTP Content-Type header is missing from the HTTP POST request. This isn't a problem with most servers, but there are servers that rejects the request without there also being a Content-Type header. RFC 1945: Any HTTP/1.0 message containing an entity body should include a Content-Type header field defining the media type of that body. Apple Dispatch 28: QuickTime Streaming uses the "application/x-rtsp-tunnelled" MIME type in both the Content-Type and Accept headers. This reflects the data type that is expected and delivered by the client and server. https://bugzilla.gnome.org/show_bug.cgi?id=793110