https login on WM 6.1?

[jigsaw962]

Hi all - I have been trying to log in to a website on my AT&T Tilt, and after I fill in the correct credentials, it always comes back to the same log in screen.

I noticed that the site is a secure "https" instead of plain http - does this have any affect on performance in WM 6.1 Internet Explorer?

The site is for simplenote [simplenoteapp.com], in case you need to see the specific problem.

Any thoughts on how to fix this?

Thanks! - mb

[JT3]

Hello, mbartner.

The "S" is for "SSL," meaning that the data is encrypted for safety. SSL has been supported in IE Mobile since at least Windows Mobile 2003FE (and probably even before that), so I think you should be okay there.

I can think of two reasons why you might be having the symptom you describe; the first is that the site is not accepting your login for some reason, which is something you would probably need to handle with the site admins. Are you able to log onto the site from a computer or other devices?

The second possibility is that the site is just not compatible with IE Mobile for some reason, since even though mobile browsers generally do support SSL, it's possible the site also relies on some other feature that IE Mobile does not support.

So basically I would recommend making sure that your logins are working correctly, and then try a different browser - Windows Mobile 6 has lots of other options, such as Opera, Netfront, and Iris. You could also contact Simple Note's support to see if they are aware of any issues using the site on a mobile browser.

[An N]

I second the recommendation to try another browser. I never use IE on my WM device.

[doctor schn]

I use Opera Mobile on my Sprint Touch Pro 2. When I try to log into Xmarks, it often takes 3 or 4 tries before it stops cycling through the same page (as you describe). I don't know of a solution.

[Ky Ry]

Have you tried Iris, Skyfire? Opera Mini? (Not Opera Mobile.)

[icefox94]

Good point. I believe my problem is unique to Opera Mobile 10(beta).

[kafalucysnow]

Try turning turbo mode on, or off. Post results.