You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2003/08/26 07:14:39 UTC

DO NOT REPLY [Bug 22721] New: - HTTP Proxy captures Request Headers by default

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=22721>.
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=22721

HTTP Proxy captures Request Headers by default

           Summary: HTTP Proxy captures Request Headers by default
           Product: JMeter
           Version: 1.9
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: HTTP
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: mramshaw@alumni.concordia.ca


As stated, the HTTP proxy captures the request headers by default.

As these will not normally vary for a given browser (and could
presumably be replaced by the default configuration settings),
I have made a patch to *not* capture the request headers,
unless specifically requested to do so (via the UI).

(Also some javadoc fixes which I have verified with j2se1.4.2).

Here are some comments from Mike Stover:

> Long ago I added the headers because I ran into some
> asp apps on IIS servers that gave 500 responses if the
> browser headers weren't there.
>
> My guess is it was depending on the user-agent info to
> be there, but I wasn't sure. Capturing the headers sent
> seemed like a good idea to ensure coverage of whatever
> the browser was doing.
>
> Making it optional is certainly a good idea.

Let me know how well this patch works (or doesn't).