<head></head><body style="line-height: 1.5; font-size: 14px;font-family: Source Han Sans;">
<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><p>Hello LIVE555 developers,</p><div>I would like to ask whether the following RTSP version handling behavior in LIVE555 is intended.</div><div>My test setup uses the ProfuzzBench RTSP/Live555 subject as the benchmark harness, but the actual tested implementation was updated to the upstream LIVE555 latest version before verification.</div><div><br></div><div>Tested target:</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>LIVE555 Streaming Media</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>Program: testProgs/testOnDemandRTSPServer</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>Version: 2026.06.24</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>Commit: fd17896e0ea37d3bb65ed6c50cc72afcd7d8e8c7</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>The server was started locally on 127.0.0.1:8554. I sent the following RTSP/2.0 requests.</div><div><br></div><div>Probe 1:</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>OPTIONS * RTSP/2.0</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>CSeq: 1</div><div>Observed result, 5/5 runs:</div><div> <span class="mce-nbsp-wrap" contenteditable="false"> </span>RTSP/1.0 200 OK</div><div><br></div><div>Probe 2:</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>SETUP rtsp://127.0.0.1:8554/wavAudioTest RTSP/2.0</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>CSeq: 1</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>Transport: RTP/AVP;unicast;client_port=1234-1235</div><div>Observed result, 5/5 runs:</div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>RTSP/1.0 200 OK</div><div><br></div><div>My understanding of RFC 7826 is that, for an RTSP/2.0 request, a server that supports RTSP/2.0 should return an RTSP/2.0 response, while a server that does not support or refuses that major version should reject it with: </div><div><span class="mce-nbsp-wrap" contenteditable="false"> </span>505 RTSP Version Not Supported</div><div>However, LIVE555 returns a successful RTSP/1.0 response to the RTSP/2.0 request. This appears to be a protocol version handling inconsistency, and may cause interoperability issues or client-side state confusion for RTSP/2.0 clients.</div><div><br></div><div>Could you please confirm whether this behavior is intended? If it is unintended, I can provide the minimized reproducer and full response logs.</div><div><br></div><div>Best regards,</div><div>Bocheng Cao</div></div>
<br><img width="1" height="1" style="display:flex" src="https://tr.qiye.163.com/datacapture/mailreport/v2/0a9f01c58bbb09bakunm2911f2bd9bb8?zone=hz&to=live-devel@lists.live555.com&tm=1782441242280&sign=55cc7e459eaf1bedbb45ac82e5480c9c&from=213220597%40seu.edu.cn&mid=AI2AqQBKKuMx*0OVXcQzvaoa&ack=0&toname=live-devel"></body>