This bug was found while tracking the root cause of bug 1111978. https://bugzilla.mozilla.org/show_bug.cgi?id=1111978#c12 Our RTSP client cannot play RTSP video on the website www.monternet.com. It is because we encounter an error while parsing the RTSP PLAY response from the server. This bug is aimed at fixing this problem so that our client could play this site.

Captured RTSP packets.

The following is the summary of RTSP PLAY request and response in the captured packets. C->S PLAY rtsp://221.181.100.53/<truncated...> RTSP/1.0 CSeq: 4 Session: 121908155919837442 S->C RTSP/1.0 200 OK CSeq: 4 Session: 121908155919837442 RTP-Info: url=trackID=1103;seq=1;rtptime=0,url=trackID=2201;seq=1;rtptime=0\r\n The URLs in RTP-Info field are not absolute URLs as we see in most cases. When parsing PLAY response, RTSP client would compare the URLs carried in RTP-Info with the URLs announced in SDP [1]. If they do not equal, it treats the situation as parsing error. [1] The URLs announced in SDP are composed of two parts: 1. The base URL from the Content-Base field in RTSP DESCRIBE response. 2. The URL in the control attribute in SDP.

My draft idea now is to concatenate the base URL and the url in RTP-info for comparison. But I need to study some spec to make sure this is the right way.

No one is actually working on RTSP for FxOS right now.