We don't control the generation of the GET request which is why truncation is
not an option.
A lenient encoding would give us the option of examining the data and
rejecting it if we find it invalid.
The parameter in question is generally rather long URLs where we would be
willing to simply extract
would not be corrupt and can be returned to caller.
We get bad encodings due to various truncation issues so it is very helpful
if we can get a lenient decoding.
Please let me know if this is something that could be looked at. I'd
volunteer dev / test time to get this in the code.
thx,
thushara
ot;);'
c9=http%3A%2F%2Fwww4.mpire.com%2Fadreview%2Fvarick.htm%
thx,
thushara
