in reply to How to use cgi param() to read unescaped url parameters

You should not make it work either way. ";" is a legal separator and if it's escaped, it's meant to be the literal character; not a super secret non-standard, literal semi-colons are now impossible, version. You should fix the code that is creating the broken URI, not create code that allows broken ones to work, because they shouldn't.

We'd love to help fix the real problem if you can show the URL generating code.

  • Comment on Re: How to use cgi param() to read unescaped url parameters

Replies are listed 'Best First'.
Re^2: How to use cgi param() to read unescaped url parameters
by marinersk (Priest) on Oct 31, 2013 at 21:13 UTC
    Oh, you are so getting a ++ tomorrow.