[Bug 793110] rtspconnection: No Content-Type header in HTTP POST requests for RTSP tunnelling

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=793110

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.13.1

--- Comment #1 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
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 at 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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.