Session ID management

[bertmac <be...@comcast.net>]

I'm measuring a Java/Websphere application, and don't really know how session
ID management is done.
Is there any reason that I should not specify both coookie management and
URL rewrite to cover my bases?
-- 
View this message in context: http://old.nabble.com/Session-ID-management-tp27577910p27577910.html
Sent from the JMeter - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org

Re: Session ID management

[Deepak Shetty <sh...@gmail.com>]

Shouldn't be a problem if you do both, but you should only use url rewriting
in Jmeter if your application actually rewrites urls.

However its pretty simple to know what your application does. Use a browser
trace tool like LiveHttPheaders in firefox , access the pages on your
application and see the logs, If you see a Set-Cookie for the session id its
uses cookies. On the first page, if the url you click has the session id in
the url the application uses url rewriting. If on subsequent clicks the urls
dont have the session id, the application supports both.

On Sat, Feb 13, 2010 at 11:17 AM, bertmac <be...@comcast.net> wrote:

>
> I'm measuring a Java/Websphere application, and don't really know how
> session
> ID management is done.
> Is there any reason that I should not specify both coookie management and
> URL rewrite to cover my bases?
> --
> View this message in context:
> http://old.nabble.com/Session-ID-management-tp27577910p27577910.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>