Page 1 of 1
session cookies not being set from rest response
Posted: Mon Oct 14, 2013 2:33 am
by greg keys
Im trying to set a login session via rest however it seems like session cookies arent being set, I tried with the proxy off by building the app and testing in real time but there seems to be a problem somewhere
session cookies not being set from rest response
Posted: Mon Oct 14, 2013 2:54 am
by maxkatz
How do you check that the session cookie is not there?
session cookies not being set from rest response
Posted: Mon Oct 14, 2013 2:59 am
by greg keys
havent figured that out specically however we do have REST calls we can make which will return a logged in users information and its not finding the validated session, it works as expected using an advanced REST client for testing but its not working on the appery build, testing app or in the browser with the proxy
session cookies not being set from rest response
Posted: Mon Oct 14, 2013 3:02 am
by greg keys
its possible that the build we are getting is not the current build, for some reason old features we deleted a while ago are still showing up in the build, is there some sort of build cache or something, maybe the apps I'm building with appery still have the proxy enabled?
session cookies not being set from rest response
Posted: Mon Oct 14, 2013 3:26 am
by maxkatz
No, there is build cache.
session cookies not being set from rest response
Posted: Mon Oct 14, 2013 3:26 am
by maxkatz
We would need to see more details, what is the expected results and what happens now, etc.
session cookies not being set from rest response
Posted: Mon Oct 14, 2013 3:27 am
by greg keys
how do we clear that build cache so we get a copy with all the current changes?
session cookies not being set from rest response
Posted: Mon Oct 14, 2013 3:29 am
by maxkatz
Sorry, I meant to say there is no build cache.
session cookies not being set from rest response
Posted: Mon Oct 14, 2013 4:17 am
by greg keys
ok found the problem this setting:
Render all pages in one HTML file (jQuery Mobile multi-page template)
when switching that off, for some reason it was loading old pages and services which had the proxy enabled.
When I switched it back to render all pages as one it worked properly.