On Monday 11 March 2002 13:13, Marco Marongiu wrote: > Tod Harter wrote: > > > > I've looked at a couple of examples but the parsers don't like & or > > > > the examples are incorrect.. If I encode the link it does not work > > > > in the browser. > > > > > > This is why I *always* try and use semi-colon as a separator in > > > querystrings rather than ampersand. Makes life a whole lot easier. > > > > Ayup. Just as a "for your info" technically the ampersand is ILLEGAL in a > > URL. Its kind of been made an "acceptable non-conformance" by the sheer > > force of common useage, but it is still not really correct, hence the > > perennial problems with encoding it. Like Matt says, use semi-colon! > > ...or use the & entity. I had the same problem minutes ago, and > solved it by encoding the ampersend. All works great now!
Oh, sure. I didn't mean to imply you couldn't encode it. Once you do that you can happily put anything in your URL. Just the raw character '&' itself is illegal, which unfortunately most web app designers don't seem to know :(. In the "Yee old days" it wasn't much of an issue. Sadly there are a lot of authoring tools and frameworks out there with broken assumptions built in. Several of them can even be blamed on me! ;o). > > --M --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
