Reminds me of a problem I had back in 1998 or so, with an app that passed a parameter called "currentgroup" to most pages. Under the current common version of IE at the time, the URLs would be oddly mangled with what looked like binary garbage appearing in them.
It turned out, of course, that ...¤... from where the currentgroup param was specified in the URL was being turned into an international currency symbol - ¤, ¤ in HTML. IE was parsing it as a character entity in the URL, despite the lack of trailing semicolon...
Buy Stuff From Amazon 
2 Comments:
Reminds me of a problem I had back in 1998 or so, with an app that passed a parameter called "currentgroup" to most pages. Under the current common version of IE at the time, the URLs would be oddly mangled with what looked like binary garbage appearing in them.
It turned out, of course, that ...¤... from where the currentgroup param was specified in the URL was being turned into an international currency symbol - ¤, ¤ in HTML. IE was parsing it as a character entity in the URL, despite the lack of trailing semicolon...
Alaric, I think you did pretty well to solve that issue as well! Sounds like a pretty nasty bug, how long did it take you to figure that one out?
Post a Comment