https://issues.apache.org/bugzilla/show_bug.cgi?id=56358
--- Comment #18 from Zach Calvert <[email protected]> --- Alright, went home and burned some of my personal time to figure this one out. I will be attaching a WAR file, some code, and a jmeter script shortly. First, make sure you have commented out your cookie manager config: # CookieManager.check.cookies=false Key elements: The request to get the cookie must be on a path not corresponding to the cookie. ie request to http://localhost:8080/cookie/get, and the Set-Cookie should have the path set like /ssc, something NOT related to the request GET query string. The next Jmeter request http://localhost:8080/ssc will not provide the cookie. Browsers IE, FireFox, and Chrome support an unrelated path setting the cookie for another path. I believe this is where the "check.cookies" filter comes into play. What I mean by this is JMeter will not allow http://localhost:8080/cookie to set a cookie with "/ssc" as the path. So, example request sequence: GET http://localhost:8080/ssc/somepath/cookie/test?cookieName=test&age=1&path=/cookie&version=1&value=sampleValue Response cookie: Set-Cookie: test=sampleValue;Max-Age=1;Path=/cookie;Version=1 Next: POST http://localhost:8081/cookie/test This SHOULD have the cookie, but it will not. I will attach my WAR, my WAR code, and my jmeter script. -- You are receiving this mail because: You are the assignee for the bug.
