Re: & url question

If you want your code to play nice with others, you should definitely:

When constructing URL strings:
- Use only \w+ for parameter names
- uri-escape (see URI::Escape) the parameter values
When parsing URL strings:
- Just use CGI.pm's param functionality. Or, for an extra buffer, use CGI::Safe.

The only "&" characters in your URL should be explicitly put there by you (or code that constructs the URL for you) as separators -- generally, all metacharacters, whitespace, etc. will be URI-escaped into %xy hex values.

Comment on Re: & url question

Replies are listed 'Best First'.
Re^2: & url question by Anonymous Monk on May 24, 2005 at 13:40 UTC
Yes, I know but that name is a name that is like that, I can't change it.	[reply]
Re^3: & url question by dorward (Curate) on May 24, 2005 at 14:46 UTC
You aren't changing it. You are representing it in a URL. In morse code the data "s" is represented as "...". In URLs, the data "&" is represented as "%26" Edit: Having reread the grandparent I now see I'm being stupid. The grandparent is good style advice, but sometimes changing things after the fact is a little difficult - especially on a short time scale. You can encode the names as well as the values of parameters though.	[reply]