This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
Why would it feel it necessary to wipe out the history or cache?
With regards to the request; if what you are after are the request parameters, and the request is a GET where the params are part of the URL, you can get the entire request URL with window.location.href. But you'll need to parse out the request parameters yourself (or find a plugin to do it).
Or is what you are actually after the headers? It's hard to tell what you are after from your post.
Thanks Bear and Jeanne. Let me explain my problem. I have a website wherein when someone hits the URL , the request is passed on to the server and from the server , redirects to my authentication page. Sometimes when the request is passed on to the server , during redirection to my authentication page , some old history or cache is coming and it invalidates my session and hence my session object is not created. How do i avoid this. I am using weblogic 10.3.
We are using Java Page Flow framework . As per the JPF framework, we are creating the HttpSession in the begin() method. Then we are setting a unique ID using setAttribute for that session. Then my request redirects to the preauth jsp page where I open a new window and set the below attributes for the authentication page and redirect to my authentication page.
When I try to submit my authentication page after entering the credentials , in my JPF Controller I'm validating the unique ID which i have already set in the begin() method.
Sometimes(out of 100% , 5 % it is failing), I am not able to get the unique ID (that i have set in the session) and my session Object is coming as null.
My Controller JPF class
Also, please note I'm creating the session in the begin method only and nowhere I'm modifying the session object.
After clearing the browser cache and session , it is working correctly.
So I thought of clearing the browser cache / history in some way!!!