Quote:
|
Originally Posted by Jason Dunn
Quote:
|
Originally Posted by rbrome
Also, why try to maintain a list of all user agents for all WAP phones? What a chore! Why not just look for "text/vnd.wap.wml" in the HTTP-ACCEPT header, (then make an exception for Firefox)? That would be much easier, IMHO. :wink:
|
Good question. We don't have a WAP portal though, so are you saying that WAP phones can render the HTML? I'm a little vague in this area... |
Ah - your mobile site is HTML? I assumed it was WML. My bad.
Some newer (non-MS) phones are designed to support HTML, but certainly not a majority. However, most new phones have WAP 2.0 browsers that support xHTML. They're not specifically designed to support HTML, but since xHTML and HTML are so similar, many are "HTML tolerant", essentially providing unofficial HTML support.
Regardless, any browser that has "text/vnd.wap.wml" in the HTTP-ACCEPT header is almost certainly a phone, and shouldn't see the "full" site by default (regardless of the markup language involved). The exception is the new Firefox browser - some versions of Firefox report "text/vnd.wap.wml" in the HTTP-ACCEPT header. But looking for Firefox in the user-agent is an easy way to work around that. It's certainly easier than trying to build a database of user-agent strings for every mobile device out there... 8O