jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: Issue with Header Manager
Date Sun, 17 Sep 2006 16:54:17 GMT
On 17/09/06, R R <> wrote:
> Hi,
> I have a need to put in a custom HTTP request and am hoping to use the HTTP
> Header Manager to do this but I am seeing a odd issue with duplicate
> variable names:
> The reqest need to be something like:
> >>Request <<
> PUT /lisa/calendar/newevent.ics HTTP/1.1
> If-None-Match: *
> Host:
> Content-Type: text/calendar
> Content-Length: xxx
> PRODID:-//Example Corp.//CalDAV Client//EN
> DTSTART:20010714T170000Z
> DTEND:20010715T035959Z
> SUMMARY:Bastille Day Party

These are body content, not headers, surely?

> But when I put these values into the HTTP Header Manager there is a
> difference with with what Jmeter thinks its sending and what is actualy
> sent. In the sample request listener everything looks ok but by using
> Etherial I can see that when a variable is duplicated only the 2nd value is
> used.

This is due to the Http implementation, not JMeter. The stand Http
Sampler uses the following method:

void key, String value)

For which the Javadoc says:

Sets the general request property. If a property with the key already
exists, overwrite its value with the new value.

NOTE: HTTP requires all request properties which can legally have
multiple instances with the same key to use a comma-seperated list
syntax which enables multiple properties to be appended into a single

> So the above header actulay shows up as...
> PUT /lisa/calendar/newevent.ics HTTP/1.1
> Host:
> If-None-Match: *
> Content-Type: text/calendar
> VERSION: 2.0
> PRODID: -//Example Corp.//CalDAV Client//EN
> DTSTAMP: 20060712T182145Z
> DTSTART: 20060714T170000Z
> DTEND: 20060715T040000Z
> SUMMARY: Bastille Day Party
> Authorization: Basic cmV6YS5yb2tuaUBvcmFjbGUuY29tOnRlc3Qx
> User-Agent: Java/1.5.0_07
> Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
> As can be seen the BEGIN and END values are only getting picked up for the
> 2nd occurance of the value in the JMX file.
> Is there a known issue with this with any workarounds?

This is working as documented.

As far as I can tell, the VCard data should be sent as part of the
BODY, not headers.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message