[Live-devel] Handle carriage return/line feed in base64Decode

[Chris Richardson (WTI)]

Hi Ross,

 

Thank you for implementing this.  I have tested your changes and everything
is working fine.


Chris Richardson

WTI

 

From: live-devel-bounces at ns.live555.com
[mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
Sent: Sunday, June 30, 2013 1:13 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Handle carriage return/line feed in base64Decode

 

 

On Jun 23, 2013, at 4:37 PM, Ross Finlayson <finlayson at live555.com> wrote:





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.

 

Rather than put CR/LF (or other whitespace) removal inside the Base-64
decoding routine, we can just add a whitespace-removing pass to the
"RTSPServer" code, before we call "base64Decode()".  I'll add this change to
the next release of the code.

 

FYI, the latest version (2013.06.30) of the code includes this change.  I
hope it works OK for you.

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/ 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20130702/c3dc65c3/attachment-0001.html>