Cookies

Gatling (Open-Source)
1

Hi

I’ve just started using Gatling, and I’m trying to get it to work with the Play Framework.

I’ve hit a problem where Gatling seems to be sending code rather than text to the server in its request header. So for example after receiving the response:

Set-Cookie: PLAY_SESSION=“e8e157a1ffed4cf4aa34df16acac1e485ecd6147-applicationId=52c6ed4b3004ae4273fc3e2b”; Path=/customer; HTTPOnly

It is subsequently sending this in the request header:

Cookie: PLAY_SESSION="“e8e157a1ffed4cf4aa34df16acac1e485ecd6147-applicationId=52c6ed4b3004ae4273fc3e2b”"; $Path="/customer"; $Domain=“localhost”

When of course it really should be this:

Cookie: PLAY_SESSION=“e8e157a1ffed4cf4aa34df16acac1e485ecd6147-applicationId=52c6ed4b3004ae4273fc3e2b” ;path=/customer; domain=localhost

Any help would be much appreciated.

Thanks

Jonny

2

Hi,

Which version do you use?
Actually, this form of Cookie is RFC6265 and it’s properly supported in Gatling 2.

3

I’m using 1.5.3

4

I’ll check if I can backport RFC6265 support in 1.5.4.
Can you upgrade to 2M3a?

5

I upgraded to 2.0.0-M3 and this has resolved my problem, thanks.

I’ll check if I can backport RFC6265 support in 1.5.4.
Can you upgrade to 2M3a?

6

Thanks for your feedback. As I said, I’ll try to backport in 1.5.4.

Cheers,

Stephane