JMeter does not handle HTTP headers not delimited by whitespace

[asfimport]

Doug (Bug 46977): According to RFC 2616, headers are field-name ":" [ field-body ] CRLF It specifically says: "Each header field consists of a name followed by a colon (":") and the field value. "

This permits headers of the form:

User-Agent:XYZ

even though we are mostly used to seeing:

User-Agent: XYZ

Unfortunately, JMeter cannot handle headers in the first form - as evidenced by the following header (emitted from a mobile device emulator):

User-Agent:OPWV-SDK/62 UP.Browser/6.2.2.1.208 (GUI) MMP/2.0

which appears in the Browser-derived Headers (after capture via HTTP Proxy Server) as:

Name: User-Agent:OPWV-SDK/6 [Note how the 2 has vanished] Value: UP.Browser/6.2.2.1.208 (GUI) MMP/2.0

I suspect this is in the header manager where it splits the headers on "\t" or " " which, though convenient, is not in line with the spec.

Severity: normal OS: All

[asfimport]

Sebb (migrated from Bugzilla): Thanks for the report.

Fixed in SVN, r762874

[asfimport]

Gregg (migrated from Bugzilla): Correct svn revision is r762874

[asfimport]

Gregg (migrated from Bugzilla): Trying to indicate the correct revision a couple of ways:

URL: http://svn.apache.org/viewvc?rev=762874&view=rev revision keyword: revision 762874 r followed by a number: r762874

[asfimport]

Sebb (migrated from Bugzilla): Just for completeness, the SVN revision reference bug was raised as

https://issues.apache.org/jira/browse/INFRA-2038

This has now been fixed, so the SVN rnnnn references now work OK.

[asfimport]

Mark Thomas (migrated from Bugzilla): Testing r762874 May be an edge case for the end of the comment