If you're writing custom code, simply set the user-agent header yourself.
If you're stuck in IE6 for WinCE, and it's just you, I think there are
registry settings you can hack.
If you have wider distribution, you might be out of luck. I think this
issue has been raised previously however. A fix
Have you tried going straight to http://twitter.com/login ? it does not
redirect to mobile version and should render in mobile IE6.
On Thu, Oct 8, 2009 at 9:37 AM, Andrew Badera and...@badera.us wrote:
If you're writing custom code, simply set the user-agent header yourself.
If you're stuck
Thanks Andy,
Changing the user agent is a possibility, although advertising that we
are a mobile device sometimes has its advantages, like defaulting to
Google's mobile page, which is a simpler, stripped down version. So as
an OEM, it's a fine balance when deciding between which big web
servers
Thanks Pavlo,
I tried, but it doesn't make a difference, despite sending a filename
index.html, the page served is still flagged as application/xhtml+xml
and coming from m.twitter.com
And this is something wget can confirm.
$ wget -U Windows CE twitter.com/login/
--2009-10-09 10:46:55--
