Re: URL safe characters?

gordonb3 wrote: 
> So how does a wrong answer to a wrong question help you?
> 
> The characters that your python app encodes are *not* URL safe. They may
> however be considered safe in other URI variants and for some obscure
> reason the LMS devs chose to not obey the strict HTML rules for internal
> used file references but write their own transcode module. To match that
> result you must do the same and the sensible thing is to use the already
> existing module like you are doing now. This also means that it is
> pointless to let your python app generate URI encoded strings in the
> HTML body as all this does is require you to decode them before being
> able to use the correct encoder.

Please, give it a rest! You are *W R O N G*. -My- Python URLs are
encoded by urllib (a standard Python library) - not by hand by me. They
*ARE* perfectly fine. However, you can -decide- not to encode certain
characters. Which is what was ORIGINALLY asked. The fact that LMS *can*
decode these proves they are correct (let alone the fact that they are
encoded by a standard library).

I was not given a wrong answer to a wrong question. The answer I was
given was perfectly correct.



*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