Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Session ID changes for a POST request
Date: Fri, 22 Aug 2008 19:09:57 +0100
Message-ID: 
 <2AB2B3C160BFC14CB0D94D437513C3BA91B382@revmail02.revenuedomain.ie>
Thread-Topic: Session ID changes for a POST request
Thread-Index: AckEXjsdafAaJ7VTTQetrM5yjV+oZAAI0dEg
From: "Fitzpatrick, Adrian" <adrianf@revenue.ie>
To: "JMeter Users List" <jmeter-user@jakarta.apache.org>


Hi,

It looks to me that you may have recorded the JSESSIONID "92714......."=
 into
the script when you originally created the script, so thats why its being
sent with every request. If you can remove this jsession portion of the URL
from you HTTP sampler, the correct JSESSION which is being included in the
cookie data should be picked up instead.=20

Alternatively, if your application and/or app server needs the JSESSION id=
 to
be in the URL, you may be able to change the URL in the HTTP sampler so=
 that
it=20
looks something like this -

http://localhost:8080/gate.do;jsessionid=3D${JSESSIONID}?action=3Dindex

i.e. its using a variable to fill in the correct value. However im not sure
if this is the correct syntax to get the value of a cookie as a variable,=
 you
can look up how to this (am sure its possible) if that doesnt work.

Regards,

- Adrian


-----Original Message-----
From: Chris Hall [mailto:chrishall_ie@yahoo.com]
Sent: 22 August 2008 14:51
To: jmeter-user@jakarta.apache.org
Subject: Session ID changes for a POST request


*************************************

This e-mail has been received by the Revenue Internet e-mail service. (IP)

*************************************


Hi all,
  I've been getting problems with Session ID's.

  I've added a HTTP cookie manager, which seems to have resolved most of my
problems, but I@ve come across an instance where the session ID is not=
 being
passed correctly to the URL.

  ie
   GET request #1:=20
        GET http://localhost:8080/welcome.do?action=3Dform
=20
        Cookie Data:
        JSESSIONID=3D195374BBEEE86BB9633B1CF93B48A03C

        Request Headers:
        Connection: keep-alive

  but on the next page
   POST request #1:

   POST
http://localhost:8080/gate.do;jsessionid=
=3D927141B2B85E34E8F586B1FEC7CED71C?act
ion=3Dindex

   POST data:
   Name=3DMyName&Password=3Dpass

   Cookie Data:
   JSESSIONID=3D195374BBEEE86BB9633B1CF93B48A03C

   Request Headers:
   Connection: keep-alive
   Content-Length: 294
   Content-Type: application/x-www-form-urlencoded

>From here, you can see the cookie has the same session ID for both=
 requests,
except for the post, the url passed is incorrect.

  am i missing something simple here? I'm very new to JMeter it has to be
said.

Rgds,
Chris
--=20
View this message in context:
http://www.nabble.com/Session-ID-changes-for-a-POST-request-tp19107615p1910=
76
15.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


************************

This message has been delivered to the Internet by the Revenue Internet=
 e-mail service (OP)

*************************

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