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 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 from Twitter would be
> nice.
>
> ∞ Andy Badera
> ∞ +1 518-641-1280
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me: http://www.google.com/search?q=andrew%20badera
>
>
>
> On Wed, Oct 7, 2009 at 8:01 PM, NaileBrotte <nailebro...@gmail.com> wrote:
> >
> > Hi,
> > I'm working on a device running Windows CE 6.0 / IE6 (not Windows
> > Mobile 6), and when accessing www.twitter.com, I'm redirected to
> > m.twitter.com (because the User Agent says "Windows CE"). The problem
> > is that IE6 doesn't handle the login page that is being sent by the
> > server because it's  marked as "application/xhtml+xml" which IE
> > doesn't handle and just offers for download.
> >
> > Is there a way to access the standard page? Or browse a fixed URL that
> > wouldn't redirect to the mobile page?
> > There must be a few devices like that with that same problem.
> >
> > Maybe the parsing of the User Agent could be made a bit more specific
> > about what has to be identified as a mobile.
> >
> > Thanks in advance.
> > NB.
> >
> >
> > wget -U "Windows CE" www.twitter.com
> >
> > --2009-10-08 11:46:33--  http://www.twitter.com/
> > Resolving www.twitter.com... 168.143.161.20
> > Connecting to www.twitter.com|168.143.161.20|:80... connected.
> > HTTP request sent, awaiting response... 301 Moved Permanently
> > Location: http://twitter.com/ [following]
> > --2009-10-08 11:46:33--  http://twitter.com/
> > Resolving twitter.com... 168.143.161.20
> > Reusing existing connection to www.twitter.com:80.
> > HTTP request sent, awaiting response... 302 Found
> > Cookie coming from twitter.com attempted to set domain to
> > m.twitter.com
> > Location: http://twitter.com/login [following]
> > --2009-10-08 11:46:34--  http://twitter.com/login
> > Reusing existing connection to www.twitter.com:80.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 3404 (3.3K) [application/xhtml+xml]
> > Saving to: `login'
> >
> >     0K ...                                                   100%
> > 24.6K=0.1s
> >
> > 2009-10-08 11:46:34 (24.6 KB/s) - `login' saved [3404/3404]
> >
> >
> >
> >
> > wget -U "Windows" www.twitter.com
> >
> > --2009-10-08 11:46:15--  http://www.twitter.com/
> > Resolving www.twitter.com... 168.143.162.116
> > Connecting to www.twitter.com|168.143.162.116|:80... connected.
> > HTTP request sent, awaiting response... 301 Moved Permanently
> > Location: http://twitter.com/ [following]
> > --2009-10-08 11:46:15--  http://twitter.com/
> > Resolving twitter.com... 168.143.162.116
> > Reusing existing connection to www.twitter.com:80.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 21063 (21K) [text/html]
> > Saving to: `index.html'
> >
> >     0K .......... ..........                                 100%
> > 54.8K=0.4s
> >
> > 2009-10-08 11:46:21 (54.8 KB/s) - `index.html' saved [21063/21063]
> >
> >
>

Reply via email to