Philip Mak wrote: > > Probably, although I haven't actually looked at the code so I'm just going > by what you're saying. > > You could change the split statement in your copy of ASP.pm and the > semicolon will work. > The patch that I'm sending him with have a split on ; as well as & > Using ampersands in delimiting query string parameters is technically > invalid HTML, because & is used to denote special characters like <, > >, ", etc. > The only thing I've seen about not using & is a slight warning against this at http://www.w3.org/TR/html4/charset.html#h-5.3.2 Authors should use "&" (ASCII decimal 38) instead of "&" to avoid confusion with the beginning of a character reference (entity reference open delimiter). Authors should also use "&" in attribute values since character references are allowed within CDATA attribute values. So I would suggest to not use both & and ; as query string delimiters, but outside of that, I wouldn't start escaping all your & to &, you could but why bother, no user agents will get this confused, as & has always been supported in query strings. --Josh _________________________________________________________________ Joshua Chamas Chamas Enterprises Inc. NodeWorks Founder Huntington Beach, CA USA http://www.nodeworks.com 1-714-625-4051 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
