K
KittyHawk
I've got an ASP.NET application using the MMIT 1.0. The app builds URL query strings dynamically. I've always used the & or & escape sequence in the past to specify an ampersand in the query string and it's worked just fine. Now, I've got users with newer WAP browsers who say that the URLs the app builds are invalid. The URL is actually displaying the escape sequence which, of course, is invalid. If I just use the ampersand it renders older WML browsers useless.
What is the best solution to this?
What is the best solution to this?