Thanks for the suggestion, but, unfortunately, that didn't appear to do the trick. I uncommented the hc.parameters.file=hc.parameters line in jmeter.properties and updated hc.parameters. We've also tried each of the different http client modes (java, hc 3.1, hc4). Still, we send requests with two Cookie headers.
I also tried removing the $Boolean, just to verify that the file is used, which made jmeter throw a classcast error. So I know the file is read by the application. Any other ideas? On Fri, Nov 11, 2011 at 12:08 PM, sebb <[email protected]> wrote: > On 11 November 2011 16:55, Archie Cowan <[email protected]> wrote: > > Hello JMeter Users, > > > > I am currently attempting to use jmeter with an application that is > > sensitive to the number of Cookie headers in requests. Somehow, my Jmeter > > test is sending a second Cookie header and this causes the application > > under test to fail. > > > > According to RFC 6265 (http://tools.ietf.org/html/rfc6265#section-5.4): > > > > "When the user agent generates an HTTP request, the user agent MUST NOT > > attach more than one Cookie header field." > > > > Can I eliminate this behavior in jmeter? My test is using HttpClient4 for > > requests and the "compatibility" mode on the Cookie Manager. I appreciate > > any help you can provide! > > As far as I can tell, HC4 should only use multiple cookie headers for > RFC 2109/2965 cookies. > > Should not make any difference, but you could try updating > hc.parameters to add the following property: > > http.protocol.single-cookie-header$Boolean=true > > Remember to enable the hc.parameters file. > > Let us know if that works or not. > > > Regards, > > > > Archie > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
