@Rob: I’ve just pushed a fix: https://github.com/excilys/gatling/issues/1732
We did take the path into account, but in case of multiple cookies with the same name, we were erroneously sending only one, instead of sending all of them but sorted.
Please tell me if it works properly now,
Cheers,
Stéphane
Unfortunately, the other cookies are still not being set for the “/app/consumer” path - the results are looking the same.
Could you send the new Charles logs for Gatling, please?
We just tried clearing out our Gradle cache as well, just in case… here’s the trace: http://cl.ly/0g1i0f1v0d3e
CONFIDENTIAL COMMUNICATION:
This email may contain confidential or legally privileged material, and is for the sole use of the intended recipient. Use or distribution by an unintended recipient is prohibited, and may be a violation of law. If you believe that you received this email in error, please do not read, forward, print or copy this email or any attachments. Please delete the email and all attachments, and inform the sender that you have deleted the email and all attachments. Thank you.
I found a bug in the path matching attribute and pushed a fix.
Please tell me that it works now… 
HI Stephane,
Sorry it took so long to respond, I was having trouble pulling down the latest snapshots. It didn’t work again - same results as before. I’m looking to change all of our tomcat apps to assign different cookie identifiers instead.
Then I don’t get it?!
I know this is time consuming for you, and I’m sorry for that, but could you get me the new Charles logs, please?
Oh wait, let me check something, I think I get it!
I get it!
Gatling’s CookieJar is fine, the problem is downstream in AsyncHttpClient that filters Cookies with the same name, which is wrong because it’s perfectly legal!
Let me see if I can work around this in Gatling, or if I have to fix AHC first.
Stay tuned!
Cheers, Stephane, I appreciate you looking into this so deeply. 
CONFIDENTIAL COMMUNICATION:
This email may contain confidential or legally privileged material, and is for the sole use of the intended recipient. Use or distribution by an unintended recipient is prohibited, and may be a violation of law. If you believe that you received this email in error, please do not read, forward, print or copy this email or any attachments. Please delete the email and all attachments, and inform the sender that you have deleted the email and all attachments. Thank you.
Delightful news, Stéphane: Things seem to be working now! Thanks for all the work on this.
CONFIDENTIAL COMMUNICATION:
This email may contain confidential or legally privileged material, and is for the sole use of the intended recipient. Use or distribution by an unintended recipient is prohibited, and may be a violation of law. If you believe that you received this email in error, please do not read, forward, print or copy this email or any attachments. Please delete the email and all attachments, and inform the sender that you have deleted the email and all attachments. Thank you.
Yippee!
Thanks a lot for helping me debugging this!