On 30/06/2008, timvanderet <[EMAIL PROTECTED]> wrote:
>
> >
> >
> >
> Oops, overlooked that bit:
>
> Servers send Set-Cookie
> Browsers send Cookie
>
> as can be seen from the Tree View Listener.
>
>
>
>
>
>
> I changed the name of the header in the http header manager from
> "set-cookie" to "cookie" meaning the header manager now looks like this:
> Name: cookie Value: JUSERCOOKIE=${jUserId}
>
> Now there is no evidence of any sort of request being sent. Before the http
> tree showed a request "set-cookie: JUSERCOOKIE=139283..." Now after the
> change there is no request shown, and the cookie still doesn't show up in
> the list under "Cookie Data"
The Header Manager does not send a request; it just provides headers
for the samplers in scope.
The cookie won't show up under Cookie Data because it is being treated
as a header, not a cookie.
> --
> View this message in context:
> http://www.nabble.com/Cookie-not-recognized-tp18142357p18200737.html
>
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
