Please, forget about cookies... Go local :) (best to me would be a localDatabase to store a hash of login and password to compare with online database hash) Btw, please do NOT ever login a user based on a single plain cookie... for security reasons.
That should solve webbrowser/standalone issue too I guess Remi Grumeau http://www.remi-grumeau.com Le 1 sept. 2010 à 21:31, "J. J." <[email protected]> a écrit : > Hi everyone - I'm relatively new to iPhone web development but my > company has an existing web application that I'm hoping someone can > help me out with. > > Our web page starts with a login screen, and once a user is logged in > they're session id is stored in a cookie which is used to bypass the > login screen whenever the user returns to the page. The problem is > this process is very erratic in when it does and does not remember the > logged in user. After some testing, I have determined the following > pattern: > > 1. Once the user has logged in, they may freely browse, close, and re- > open the page as well as other pages, and the user will always remain > logged in when they return to our web page, as expected. > > 2. If the user is logged in, leaves our web page open and presses the > iPhone Home button, they can re-open Safari and the web page will > appear with the user logged in, as expected. > > 3. If the user is logged in, closes the page (via the bottom right > button, not sure if it's pages/windows/etc.) and then presses the > iPhone Home button, when they return to Safari and browse back to the > web page the user will NOT be logged in anymore. > > 4. If I use Safari to add the page to the Home Screen and launch it > from there, it will never be logged in. If I use the link from the > home screen to log in, close and re-open, it will not be logged in. If > I use Safari to log in, leave the page open and close Safari, then use > the home screen link, the user will not be logged in - even though he > can then return to Safari and will be logged in there. > > The home screen business seems to be a different issue altogether, but > most importantly I need to know why Safari seems to lose the cookie > when the browser is closed, unless the page is left open and active > when closing, which allows the user to re-open Safari and still be > logged in. > > I've tried examining our code for problems with storing cookies, but > the weirdness of the issue makes me unsure if it's an issue with the > browser or our web page. Also, our same cookie functions work > perfectly on Android and PCs. If anyone could give me the slightest > hint as to what might be the problem or where to go from here, it > would be greatly appreciated. Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "iPhoneWebDev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/iphonewebdev?hl=en. > -- You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en.
