https://issues.apache.org/bugzilla/show_bug.cgi?id=56605
Bug ID: 56605
Summary: CookieManager not respecting [Cache-control:
no-cache="set-cookie, set-cookie2"]
Product: JMeter
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: critical
Priority: P2
Component: HTTP
Assignee: [email protected]
Reporter: [email protected]
This problem I faced with WebSphere Portal and the problem as following
1.Call page (i.e. /login)
2.WSP sends 302 with following :
2.A. set-Cookies i.e. X1
2.B. Cache-control: no-cache="set-cookie, set-cookie2"
3.C. Location (new location, i.e. /login2)
Having the JMeter call "/login" and with follow redirect or redirect
automatically will simply send JMeter into infinite loop. WSP insist that the
call after the 302 to NOT have the cookie X1 as the header was also instructing
the calling NOT to store such cookie with (Cache-control:
no-cache="set-cookie, set-cookie2"). All Browsers do respect that and call the
new page location "/login2" WITHOUT the "X1" cookie.
This gave us very very hard time and simply made it almost impossible to use
JMeter with WSP.
This also opened the our eyes for 2 other limitations in JMeter.
1. PostProcess, only apply to the last call in "follow redirect" chained
sampler, if this can be run in every call, we could have simply cleared the bad
cookie ourselves.
2. We even went as far as creating our own follow redirect loop. But the
problem we couldn't find a way to group or ignore the 302 calls (i.e. in the
tree view)
--
You are receiving this mail because:
You are the assignee for the bug.
