Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Mercious

  • Rank
  1. I could potentially link you to a SO question where i have a very indepth analysis of this behavior going on. It indeed does happen and there is no logical reason as to why it happens. Nothing in my code ever makes the ajax-script set that second cookie and yet it magically appears after session timeout. I swear to you, its weird as ###### and noone as figured out what causes it yet.
  2. Thats an interesting point. I always thought that session timeout is something different as no session at all.So, i guess the tomcat is handeling the sessions in the background and invalidates them as soon as they expire. Meaning a users request with a timed out session is esentially the same as a requesrt by a user that is not logged in?Then, i infact know where this happens in my code and i might be able to adjust it.I just hope this fixes my original problem. The problem is that when i trigger a session timeout with a specific ajax-script, this ajax-script stops working after i logg back i
  3. Thats the point, i really dont. I feel like tomcat has a standard implementation that also supports things such as migrating session among server cluster nodes.At no point in my source code am i checking for session timeouts, yet session timeouts do happen and i can also adjust the time in the web.xml file. I have not implemented this functionality, so there are 2 options: Its either a standard implementation by the tomcat server OR the Hybris Platform, which my software is based on.
  4. Do you not understand the idea behind the approach that he is suggesting or are you just absolutely unable to get hold of how you would go about it?Where exactly are you encountering a problem, at what step of his suggested approach? What have you tried and what isnt working or what do you not understand?
  5. I get the idea, however this is both not necessary as well as the wrong level of problem i am dealing with. Ajax-Requests are already marked with "X-Requested-With" and then the appropiate value in their Request-Header. However, the problem i have is that in terms of session-handeling: The tomcat handles this. I do not have access to what happens if a request uses a timed out session. I do not act on this, the tomcat server does. And even if i define filters, for example, i STILL am only granted access AFTER the tomcat has already dealt with the session-timeout. I hope this makes clear wha
  6. https://www.google.com/?gfe_rd=cr&ei=tWn5VIjbEqmx0wXuv4LADA#q=1+USD+to+INR
  7. Thanks for the effort, however it wasnt just a random guess from my side. Ajax-calls do not ever receive notification incase the server returns a 302. The browser jumps in before the ajax-script receives information. It then fires (the browser) a new ajax-request for the resource mentioned in the Location-Header. And THEN the ajax gets the response of whatever is returned by that server upon that second request.
  8. Hey there, i have a Java MVC Web Application that uses the Spring-Library for the Backend and then JSP files for the frontend. Now, in various JSP files i am using Ajax to have some smooth design when needed. This whole application is running on an Apache Tomcat Server. I have to admit that i am still very new in the whole Web-Development thing, so bare with me.Following problem: In the current state, i feel like the tomcat server is automatically handeling the Sesions, including session-timeouts. So, i can specify the time when a session is supposed to count as timed out and eve
  • Create New...