DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25752>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25752 HTTP Cookie isn't rightly ordered. Summary: HTTP Cookie isn't rightly ordered. Product: JMeter Version: 1.9.1 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: HTTP AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I tried recording web-access with HTTP Proxy and Recoding Controller and run it. Before run it, I added HTTP Cookie Manager. Target is Tomcat's Servlet Examples. Recorded access is: 1) /index.jsp 2) /examples/servlets/index.html 3) /examples/servlet/SessionExample 4) /examples/servlet/SessionExample with parameter 5) /examples/servlet/SessionExample with other parameter When run it, 3),4) and 5) must be on the same session, but result is NOT. I looked at "View Results in Tree" and check cookie: 1) receive: Set-Cookie: JSESSIONID=<<cookie1>>; path=/ 3) send : Cookie: JSESSIONID=<<cookie1>> receive: Set-Cookie: JSESSIONID=<<cookie2>>; path=/examples 4) send : Cookie: JSESSIONID=<<cookie1>> JSESSIONID=<<cookie2>> receive: Set-Cookie: JSESSIONID=<<cookie3>>; path=/examples 5) send : Cookie: JSESSIONID=<<cookie1>> JSESSIONID=<<cookie3>> receive: Set-Cookie: JSESSIONID=<<cookie4>>; path=/examples In RFC2965 "HTTP State Management Mechanism" Section 3.3.4, > If multiple cookies satisfy the criteria above, they are ordered in > the Cookie header such that those with more specific Path attributes > precede those with less specific. Above 4) and 5) sending cookie isn't suitable for that, so Tomcat would confused. 4) sending must be: 4) send : Cookie: JSESSIONID=<<cookie2>> JSESSIONID=<<cookie1>> I think that should be fixed. Removing 1) from TestPlan and run it, 3), 4) and 5) is on the same session, and 4) and 5) don't receive Set-Cookie: header, that is workaround. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
