[rtmpdump] Escape encoding

[NhJm]

The \xx escaping only works for librtmp URL parameters (ex. 'rtmp://
freeview.fms.visionip.tv/live/tvnetwork-hellenictv-sigma-hsslive-25f-4x3-SDhtcUrl=rtmp://
freeview.fms.visionip.tv/live/tvnetwork-hellenictv-sigma-hsslive-25f-4x3-SDh\0D\0Aplaypath=tvnetwork-hellenictv-sigma-hsslive-25f-4x3-SDh\0D\0A
live=1')

However, rtmpdump *will* properly urldecode (ie. %xx) the playpath (but not
the app!):

rtmpdump -r "rtmp://
freeview.fms.visionip.tv/live/tvnetwork-hellenictv-sigma-hsslive-25f-4x3-SDh%0D%0A"
--live -o foo.flv

On Fri, Oct 19, 2012 at 6:10 PM, Steven Penny <svnpenn at gmail.com> wrote:

> This site
> http://kanalia.eu/player.php?id=91
>
> provides a challenge for me. The parsed playpath end with a Carriage
> Return,
> Line Feed. This was discussed on the forums.
>
> http://stream-recorder.com/forum/help-getting-greek-channel-work-rtmpdump-t13743.html
>
> A few solutions were offered up, including
>
> - remove CRLF and prepend "mp4:" to playpath
> - remove CRLF and append ".mp4" to playpath
> - pass a literal Carriage return using Bash and $'\r'
>
> KSV has noted that these solutions are nonstandard and might not be future
> proof. I noticed in the MAN this paragraph
>
> > Special characters in values may need to be escaped to prevent
> > misinterpretation by the option parser. The escape encoding uses a
> backslash
> > followed by two hexadecimal digits representing the ASCII value of the
> > character. E.g., spaces must be escaped as \20 and backslashes must be
> escaped
> > as \5c.
>
> This looks promising, but after trying to append "\0d\0a" or just "\0d", it
> appears "not to work".
> _______________________________________________
> rtmpdump mailing list
> rtmpdump at mplayerhq.hu
> https://lists.mplayerhq.hu/mailman/listinfo/rtmpdump
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mplayerhq.hu/pipermail/rtmpdump/attachments/20121020/6fb7d121/attachment.html>