Just a quick post to say that the mobile version of chrss now works properly with the Nokia 6300 built-in browser. This happens to be the phone I have and it's very much a phone (not a web-browsing device), so the mobile version is mostly for when I'm not at a computer and want to check my games and maybe make a move. I'd been using Opera Mini to access the mobile version before, but hadn't quite figured out why the native browser wasn't working.
For those who might want to know of one of the quirks of this browser (and it will be more or less the same for similar Nokia Series 40 phones) it appears that if you issue a (302) redirect after a post request then the browser re-posts the data to the redirect URL. So in chrss when logging in it was doing this:
POST login info (user and pwd) to /mob/login
302 Redirect sent to go to /mob/ after info confirmed
POST login info (user and pwd) to /mob/
Whereas a regular browser would do this:
POST login info (user and pwd) to /mob/login
302 Redirect sent to go to /mob/ after info confirmed
GET /mob/
As this meant there were some unexpected parameters Turbogears was throwing an exception. As a workaround I've changed my mobile login code to remove the user and pwd params before they cause any trouble.
In the end a simple fix, but as always testing things out an a real phone make things take a good while longer than I'd like.
updated: 2008-11-22 06:54:43