On Wed, Oct 24, 2012 at 7:29 PM, Steven Penny <svnpenn@gmail.com> wrote:
Even if I use your clever "space" trick, the server in question will still
reject other encoded characters. Notice I encoded the final "h" of the playpath,
and that I used "-y" with "official" RtmpDump in order to avoid decoding for the
purpose of this example.
It is up to the server's code to parse URLs. It is the responsibility of the user to provide the server with URLs that the server can handle.
The _official_ RTMP client does not decode URLs prior to sending them to the server, therefore rtmpdump should not be decoding URLs either.
nictv-sigma-hsslive-25f-4x3-SD%68 " -V
There's nothing we can do to fix the fact that the server (some version of Wowza, perhaps running some custom code) is not designed to handle urlencoding. (And I do mention "custom code" because the thought that Wowza itself requires whitespace at the end of a playpath scares me.)