DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38256>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38256 Summary: Set-cookie headers with no "path" attribute incorrectly processed by CookieManager Product: JMeter Version: Nightly (Please specify date) Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: HTTP AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] JMeter's HTTP CookieManager (as of 2.1.20060112) processes set-cookie headers by initially setting the new cookie's path to the same path as the requested URL (modified slightly to trim the terminal page name). When a set-cookie header comes in with no path attribute, the URL's path is left in the cookie and that path is used as the lookup key. This is different than contemporary browsers that use the root path (i.e., "/") as the path for set-cookie headers that lack a path attribute. The current behavior can cause many requests to set cookies with incorrect path causing downstream failures for HTTP requests that need cookies that would ordinarily be passed becauese thay have a root path. The problem seems to be lines 327 through 336 of: org.apache.jmeter.protocol.http.control.CookieManager ...method setCookieFromHeader() -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
