Re: Why does CGI::query_string make semicolons the rule, not the exception?

It's not the browser which processes the querystring separator, it's the server side which needs to know to process the semicolon. So if you're using a recent CGI.pm or Apache.pm on the server side, everything's fine. But there's a lot of other CGI processing modules (mostly for other languages) which cannot process the semicolon separator (hit me two times in the last six months).

You can find the ";" proposal in RFC 1866, section 8.2.1.

Comment on Re: Why does CGI::query_string make semicolons the rule, not the exception?

Replies are listed 'Best First'.
Re: Re: Why does CGI::query_string make semicolons the rule, not the exception? by tachyon (Chancellor) on Apr 13, 2004 at 15:34 UTC
It is easy to change the behaviour as noted above. I think it is wrong for similar reasons to you. If you have a look at the defaults for CGI::Simple you will see that many of the defaults are different. cheers tachyon	[reply]
Re: Re: Why does CGI::query_string make semicolons the rule, not the exception? by esharris (Monk) on Apr 27, 2004 at 18:30 UTC
The semicolon separator didn't work here. <META HTTP-EQUIV="Refresh" CONTENT="0;URL=http://www.free-cgi.com"> If the url is a script with multiple parameters, my server doesn't like semi-colon separators. Here, I had to go back to ampersands.	[reply]