https://issues.apache.org/bugzilla/show_bug.cgi?id=56358
--- Comment #2 from Zach Calvert <[email protected]> --- What value is the SetCookie coming back with? It will work for "/", but not for anything where the port and path are specified, and this may be the difference. I was under the impression the port was the problem, but perhaps it is because I'm setting the path. I'll try to specify the request ins and outs that I'm currently dealing with. Request 1: GET http://rhel55:10008/custom/simulated/1.0/sso?generate=true Response: Response headers: HTTP/1.1 200 OK Content-Type: text/xml Set-Cookie: simulatedCookie=Tk9URk9SUFJPRFVDVElPTjEzOTY5MDE3NDE5MzF8MTIzNDU2Nzg5MA==;Max-Age=120;Path=/ssc;Version=1 Request 2: POST http://rhel55:10001/ssc/auth/1.0/validate The 2nd request matches the same domain, with the "/ssc" path as specified in the cookie. Again, this works for browsers IE, FireFox, and Chrome, so I believe there is a problem to JMeter. I can open a browser to http://rhel55:10008/custom/simulated/1.0/sso?generate=true and then open the same browser to GET http://rhel55:10001/ssc/auth/1.0/validate and the cookie is sent. My differences in my actual code as listed above are a) the Path is specified, max-age is specified, and version is specified. b) The path is a full path (I specify /ssc but the next request path is /ssc/auth/1.0/validate) c) The second request is a POST, not a get in the jmeter script -- You are receiving this mail because: You are the assignee for the bug.
