rtspconnection: also add Content-Type to HTTP POST request when tunnelling
authorSebastian Cote <sebas642@yahoo.ca>
Fri, 2 Feb 2018 00:00:23 +0000 (00:00 +0000)
committerTim-Philipp Müller <tim@centricular.com>
Thu, 8 Feb 2018 16:08:03 +0000 (16:08 +0000)
commit9e77d9cacf5960c54bb0a26688208d898b380ea0
tree38c7207d12648d094176a012cd557b73c912e1b3
parentbc604f35978227c8885665c4a44d7a54665b70a2
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
gst-libs/gst/rtsp/gstrtspconnection.c