pbodnar opened a new issue, #6051: URL: https://github.com/apache/jmeter/issues/6051
### Expected behavior JMeter HTTP Cookie Manager should delete a cookie even if `Comment` attribute is present in the "cookie-deleting" (typically via the attribute `Max-Age: 0`) `Set-Cookie` header. This request is supported by the fact that both Firefox and Chrome do so. Also, the [RFC](https://www.ietf.org/rfc/rfc6265.txt) seems to be clear about this: > ... > 6. Process the attribute-name and attribute-value according to the > requirements in the following subsections. (Notice that > attributes with unrecognized attribute-names are ignored.) ### Actual behavior Cookie is still sent on follow-up requests, although it should have been deleted. ### Steps to reproduce the problem 1. Add "HTTP Cookie Manager" to a JMeter test. Leave Cookie Policy combobox set to the default value: "standard". 3. Use a "HTTP Request" sampler to call a service returning a cookie (e.g. named `TGC`). 3. Use a "HTTP Request" sampler to call a service which returns a cookie-deleting "Set-Cookie" header (e.g. `Set-Cookie: TGC=ABCD; Version=1; Comment="Logging you out"; Max-Age=0; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/`). 4. Use a "HTTP Request" sampler to call another service on the same site. 5. After running the test, check whether cookie was still sent by JMeter in the last HTTP request. ### JMeter Version 5.5, 5.6.2 ### Java Version not relevant ### OS Version _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
