<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi Ross,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I recently came across a client who sends our LIVE555 based RTSP server an HTTP message with a base64 encoded RTSP command that contains CR/LF. It seems fairly standard for a base64 decoder to support CR/LF, at least on 4 char boundaries, so I wrote up a patch to base64Decode to allow this. Then I discovered how the fragmented base64 message reading is implemented in RTSPServer and determined that the fix would not be so simple.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have pasted the relevant part of the RTSP conversation, for your information. Note that the client (not under my control) is using a very old version of LIVE555, but that is irrelevant to the test being performed, which is that the server supports base64 data with CR/LF.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>accept()ed connection from 192.168.2.100<o:p></o:p></p><p class=MsoNormal>RTSPClientConnection[0x5cc908]::handleRequestBytes() read 212 new bytes:GET /swVideo HTTP/1.0<o:p></o:p></p><p class=MsoNormal>User-Agent: ONVIF Filter (LIVE555 Streaming Media v2009.11.27)<o:p></o:p></p><p class=MsoNormal>x-sessioncookie: 0695c54a1abd2adfb783b89<o:p></o:p></p><p class=MsoNormal>Accept: application/x-rtsp-tunnelled<o:p></o:p></p><p class=MsoNormal>Pragma: no-cache<o:p></o:p></p><p class=MsoNormal>Cache-Control: no-cache<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>parseRTSPRequestString() failed; checking now for HTTP commands (for RTSP-over-HTTP tunneling)...<o:p></o:p></p><p class=MsoNormal>parseHTTPRequestString() succeeded, returning cmdName "GET", urlSuffix "swVideo", sessionCookie "0695c54a1abd2adfb783b89", acceptStr "application/x-rtsp-tunnelled"<o:p></o:p></p><p class=MsoNormal>Handled HTTP "GET" request (client output socket: 31)<o:p></o:p></p><p class=MsoNormal>sending response: HTTP/1.0 200 OK<o:p></o:p></p><p class=MsoNormal>Date: Thu, 19 Aug 1982 18:30:00 GMT<o:p></o:p></p><p class=MsoNormal>Cache-Control: no-cache<o:p></o:p></p><p class=MsoNormal>Pragma: no-cache<o:p></o:p></p><p class=MsoNormal>Content-Type: application/x-rtsp-tunnelled<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>accept()ed connection from 192.168.2.100<o:p></o:p></p><p class=MsoNormal>RTSPClientConnection[0x5d1788]::handleRequestBytes() read 281 new bytes:POST /swVideo HTTP/1.0<o:p></o:p></p><p class=MsoNormal>User-Agent: ONVIF Filter (LIVE555 Streaming Media v2009.11.27)<o:p></o:p></p><p class=MsoNormal>x-sessioncookie: 0695c54a1abd2adfb783b89<o:p></o:p></p><p class=MsoNormal>Content-Type: application/x-rtsp-tunnelled<o:p></o:p></p><p class=MsoNormal>Pragma: no-cache<o:p></o:p></p><p class=MsoNormal>Cache-Control: no-cache<o:p></o:p></p><p class=MsoNormal>Content-Length: 32767<o:p></o:p></p><p class=MsoNormal>Expires: Sun, 9 Jan 1972 00:00:00 GMT<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>----------<o:p></o:p></p><p class=MsoNormal>Below you can see that the base64 input has line breaks, which the decoder does not handle.<o:p></o:p></p><p class=MsoNormal>----------<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>parseRTSPRequestString() failed; checking now for HTTP commands (for RTSP-over-HTTP tunneling)...<o:p></o:p></p><p class=MsoNormal>parseHTTPRequestString() succeeded, returning cmdName "POST", urlSuffix "swVideo", sessionCookie "0695c54a1abd2adfb783b89", acceptStr ""<o:p></o:p></p><p class=MsoNormal>Handled HTTP "POST" request (client input socket: 35)<o:p></o:p></p><p class=MsoNormal>RTSPClientConnection[0x5cc908]::handleRequestBytes() read 210 new bytes:REVTQ1JJQkUgcnRzcDovLzE5Mi4xNjguMi42Mjo4NTU0L3N3VmlkZW8gUlRTUC8x<o:p></o:p></p><p class=MsoNormal>LjANCkNTZXE6IDANCkFjY2VwdDogYXBwbGljYXRpb24vc2RwDQpVc2VyLUFnZW50<o:p></o:p></p><p class=MsoNormal>OiBPTlZJRiBGaWx0ZXIgKExJVkU1NTUgU3RyZWFtaW5nIE1lZGlhIHYyMDA5LjEx<o:p></o:p></p><p class=MsoNormal>LjI3KQ0KDQo=<o:p></o:p></p><p class=MsoNormal>Base64-decoded 208 input bytes into 156 new bytes:DESCRIBE rtsp://192.168.2.62:8554/swVideo RTSP/1ã?56W¢?66WC¢?6Föâ÷6G?W6W"ÔvVç@: ONVIF Filter (LIVE555 Streaming Media v2009.11ã#r?Ð<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Chris Richardson<o:p></o:p></p><p class=MsoNormal>WTI<o:p></o:p></p></div></body></html>