# Cookies

**URL:** <https://community.gatling.io/t/cookies/760>\
**Category:** Gatling (Open-Source)\
**Created:** [January 3, 2014, 5:57pm UTC](https://community.gatling.io/t/cookies/760 "2014-01-03T17:57:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonny\_Cavell](https://avatars.discourse-cdn.com/v4/letter/j/e480ec/32.png) [@Jonny\_Cavell](https://community.gatling.io/u/Jonny_Cavell)\
**Post date:** [January 3, 2014, 5:57pm UTC](https://community.gatling.io/t/cookies/760/1 "2014-01-03T17:57:21Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [January 3, 2014, 7:34pm UTC](https://community.gatling.io/t/cookies/760/2 "2014-01-03T19:34:45Z")

</div>

Hi,

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

---

<div class="post-metadata">

**Author:** ![Jonny\_Cavell](https://avatars.discourse-cdn.com/v4/letter/j/e480ec/32.png) [@Jonny\_Cavell](https://community.gatling.io/u/Jonny_Cavell)\
**Post date:** [January 3, 2014, 7:36pm UTC](https://community.gatling.io/t/cookies/760/3 "2014-01-03T19:36:56Z")

</div>

I’m using 1.5.3

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [January 3, 2014, 7:45pm UTC](https://community.gatling.io/t/cookies/760/4 "2014-01-03T19:45:40Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Jonny\_Cavell](https://avatars.discourse-cdn.com/v4/letter/j/e480ec/32.png) [@Jonny\_Cavell](https://community.gatling.io/u/Jonny_Cavell)\
**Post date:** [January 5, 2014, 5:51pm UTC](https://community.gatling.io/t/cookies/760/5 "2014-01-05T17:51:31Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [January 5, 2014, 6:57pm UTC](https://community.gatling.io/t/cookies/760/6 "2014-01-05T18:57:47Z")

</div>

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

Cheers,

Stephane