Re: URL safe characters?

gordonb3 wrote: 
> That's what I'm saying - that's why you must not push full URI encoded
> strings to the plugin because at that level the strings are supposed to
> be decoded with the exception of spaces (and possible other characters
> that conflict with Perl functionality)

Please, this is silly. Look at the LMS supplied MusicMagic DSTM mixer -
this calls fileURLFromPath for the returned music paths. So, that is
converting a path into a file URL. The usage of file URLs is *correct*
here. My URLs from the Python code pecent encode more than LMS does, and
that was *all* I was querying.

*All* I originally asked was what the URL safe characters were. That has
been answered.



*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
(Use http: //SERVER:9000/material/?debug=json,cometd to also see update
messages, e.g. play queue) 2. Open browser's developer tools 3. Open
console tab in developer tools 4. REQ/RESP messages sent to/from LMS
will be logged here.
------------------------------------------------------------------------
cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686
View this thread: http://forums.slimdevices.com/showthread.php?t=115875