I have a test for a new secured site that requests a secured page, assumes the login page is returned instead, fills out the login form, submits it, and then tests to make sure we are now at the originally requested form.
My test passes the first time I run it. When I hit the run button again, it fails. saying it went straight to the desired page. If I wait a long it, it works.
My assumption is that the WebSphere 5 App Server is recognizing the client as already logged in, but I thought this couldn't happen since a new WebConversation is created EVERY time.
I have used HTTPUnit for years and never seen behavior like this.
Is there something I can clear on the HTTPUnit side to keep the App Server from remembering me from a previous WebConversation?
Thanks!
-Steve-
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If anyone can offer any ideas, or help brainstorm what could be causing this behavior, that would be so helpful.
I have tried several different browsers. They are behaving normally. If I close and then reopen the browser, I have to re-login. the server does NOT remember my having logged in.
With HTTPUnit, the server does remember I am logged in, even though I have destroyed, and then re-created the WebConversation.
Any ideas?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a test for a new secured site that requests a secured page, assumes the login page is returned instead, fills out the login form, submits it, and then tests to make sure we are now at the originally requested form.
My test passes the first time I run it. When I hit the run button again, it fails. saying it went straight to the desired page. If I wait a long it, it works.
My assumption is that the WebSphere 5 App Server is recognizing the client as already logged in, but I thought this couldn't happen since a new WebConversation is created EVERY time.
I have used HTTPUnit for years and never seen behavior like this.
Is there something I can clear on the HTTPUnit side to keep the App Server from remembering me from a previous WebConversation?
Thanks!
-Steve-
If anyone can offer any ideas, or help brainstorm what could be causing this behavior, that would be so helpful.
I have tried several different browsers. They are behaving normally. If I close and then reopen the browser, I have to re-login. the server does NOT remember my having logged in.
With HTTPUnit, the server does remember I am logged in, even though I have destroyed, and then re-created the WebConversation.
Any ideas?