google chrome - Only Cookie JSESSIONID set from first Login request is not sent in subsequent requests? -


i not able understand what's going on. on 1 of env. of webapp (written using extjs 4.0) - see login request completes subsequent request fails 401.

when digged bit more found in browser(f12) 1st request's response header has jsessionid, set cookie, 2nd request doesn't send in request headers. that's why 2nd request creates new session , returns new jsessionid.

in client code request sent,
ext.ajax.request({url:'', callback..}) - there no explicit setting of jsessionid or cookie.

strange part not cookie keys missing, jsessionid, means cookies not disabled , set browser.

why browser not sending jsessionid? tried in firefox/chrome both.

also happening in local env., qa env. of webapp working fine.

i figured out myself.. issue http://tomcat.apache.org/migration-7.html#session_cookie_configuration

thanks people spent time reading question.


Comments

Popular posts from this blog

c++ - Difference between pre and post decrement in recursive function argument -

php - Nothing but 'run(); ' when browsing to my local project, how do I fix this? -

php - How can I echo out this array? -