On 12/23/05, Darren Chamberlain <[EMAIL PROTECTED]> wrote: > * Cees Hek <ceeshek at gmail.com> [2005/12/23 08:50]: > > Just wondering if it would it be worth it to join them with a ';' > > instead? I am guessing a lot of people depend on the fact that the > > URL is already being escaped, and the ';' does not need to be escaped > > like the & does. Or maybe make that an option somewhere... > > I considered making this an option, but I didn't think of it in that > light. I know that CGI.pm supports this style of query string, but does > every web server understand it? If this is made to be the default, will > it cause problems?
Web servers and web browsers don't need to know about the query string. It is just the application that parses the query string that needs to support this format (ie your perl scripts). And I am fairly sure that most of the common perl modules on CPAN that parse query strings can handle this (at least URI, CGI.pm CGI::Simple and CGI::Minimal do). What it comes down to is splitting the query string on [&;] instead of just &, so it is not really a major effort to support these URLs in a query parser. Cheers, Cees _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
