[Bug 757118] rtspconnection: Problem when parsing vendor specific RTSP response with data after Content-Length

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Wed Oct 28 04:01:17 PDT 2015


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

--- Comment #8 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
Yes, but I didn't understand it :) How is all this related to the timeout? Also
this should be explained in code or commit message too.

The parser should fail and reset itself, behaviour should be:
- Content-Length: 0 => except 0 bytes body and then \r\n\r\n
- See \r\n
- See other stuff that is not an \r followed by an \n => "Method not supported"
and reset parser state
- See other stuff ("framerate: 30" in your case) with clean parser state that
is not a RTSP message => Skip over it and keep clean parser state. Report
"Method not supported" unless we already did that since the last valid RTSP
message start we found (so not in your case)

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


More information about the gstreamer-bugs mailing list