[Bug 757118] New: [base-plugin/rtsp] Problem when parsing vendor specific RTSP resopnse

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 757118
           Summary: [base-plugin/rtsp] Problem when parsing vendor
                    specific RTSP resopnse
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: major
          Priority: Normal
         Component: gst-plugins-base
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: realbrightster at gmail.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 314107
  --> https://bugzilla.gnome.org/attachment.cgi?id=314107&action=edit
patch file_1

Above is abnormal RTSP response from specific IP camera vendor:

"
RTSP/1.0 200 OK
CSeq: 7
Content-Length: 0
Content-Type: text/parameters
Session: 276550300

framerate: 30
"
As you can see, they send message-body but content-length is zero, in response
of keep-alive request (e.g. get parameter)

so that "framerate: 30" would be ignored by parse_line(..)
at this stage every things OK.
However we got trouble when parsing next response from server.
Because read_ahead stay in "READ_AHEAD_CRLF" state ('f'ramerate)

To resolve this problem, I think it have to be initialized to default value (0)
when create new build (build_next, STATE_START) as attached patch

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