we have recently migrated our web application from extjs 2.0 to extjs 4.0.7.
After changing and adapting code to the new version it seems that it works perfectly but actually not.
Our application is JEE application:
EXTJS -> Ajax/JSON -> Struts 1.x -> EJB 2.x ->etc...
Before migrating it worked perfectly for years.
We recently decided to migrate to ExtJS 4.0 for browser compatibility reasons, but since we have a problem.
At first connection server (WAS 7.0) detects there is no sessions and redirect to the login form, then create a JSESSIONID that is stored in a cookie by the browser.
So far everything is normal, but when we browse application (ajax request or not) then the browser is suddenly not sending JSESSIONID anymore:
- with IE it happens very often (3 or 4 requests maximum)
- with FF less often (about every 20 mins)
It seems that the information is still in the cookie but the param is not forwarded in the request. Then of course the server is forwarding to the authentication form. We use FF + Firebug and IE + WebDev. to trace request/response headers
We never faced this behavior before the migration.
Why this happen from ExtJS 4.0. Is there some thing important to know about CookieProvider?
Why do we have a different behavior between FF and IE?
If someone could help, thank you in advance.