Closed GoogleCodeExporter closed 8 years ago
my experience with multiple layers of URL encodings is that really the only way
to go is to be strict and well defined, and not try to guess whether one or
more decodings are necessary (because there will always be cases where the
guess is wrong and there's no work-around).
It's a bit unfortunate that web seed URLs in .torrent files kind of require
some heuristic to maybe decode them. I would prefer the exo-open users would
file a bug against it, or against whatever source it's getting encoded urls
from.
For example, if you type into your browser: "http%3a%2f%2fwww.apple.com", it
won't load apple's website.
Original comment by arvid.no...@gmail.com
on 2 Jun 2015 at 11:50
Original issue reported on code.google.com by
hammered...@gmail.com
on 30 May 2015 at 4:23