We've had an error that took a while to trace, and whilst we've solved it I'd like to get a better understanding of what was happening behind the scenes.
We're building an app that also acts as an API for an iOS app. Profile pictures are stored inside the /webroot/img folder, and the path to them is stored in the users table. When the users table points to an image that no longer exists (as happened when we moved from a test to a beta server) the web handles the error gracefully. If the url to a missing image is placed in a browser address bar we get a missing ImgController error, but the user remains logged in. When the iOS app tries to retrieve a missing image (and the error is not handled correctly) the user is being logged out. We've rectified the error by changing the iOS code but I'm keen to understand what might have been happened inside the Session. Can anyone shed any light please?
--
Like Us on FaceBook
https://www.facebook.com/CakePHP Find us on Twitter
http://twitter.com/CakePHP ---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to
cake-php@googlegroups.com.
Visit this group at
http://groups.google.com/group/cake-php.
For more options, visit
https://groups.google.com/d/optout.
No comments:
Post a Comment