| 1:09 am on Mar 19, 2005 (gmt 0)|
I think there is a suggestion that server-side processes should also be prepaed to accept a colon as well as an ampersand. Not sure how many have implemented this.
| 2:40 am on Mar 19, 2005 (gmt 0)|
I think what you want is %26, which is the URL-encoded hexadecimal escaped value for the ampersand; not &, which is the HTML named, character entity.
Parenthetically, it's easy to get URL-encoded values by just typing something like the following in your browser's location window:
| 8:14 am on Mar 19, 2005 (gmt 0)|
I read that %26 should only be used when you want to use an ampersand in the URL but not as a key delimiter in a query string.
For example, I noticed that when I search in Google for "encoding & ampersand", then the resulting URL in the browser address bar is something like:
Ony the non-delimiting ampersand (and semi-colon) has been encoded. The page source for that Google search still shows that delimiting ampersands are NOT encoded.
| 10:45 am on Mar 19, 2005 (gmt 0)|
There is confusion here.
| 2:05 pm on Mar 19, 2005 (gmt 0)|
| 5:22 pm on Mar 19, 2005 (gmt 0)|
Thanks guys. I was given confused by this previous thread [webmasterworld.com] which did discuss ampersands in location.href, but that was for xhtml.