Summary: | Allow overriding Host and other restricted headers | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Hari Krishna Dara <haridara> |
Component: | HTTP | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | 2.4 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Hari Krishna Dara
2011-05-21 01:05:30 UTC
Thanks for the information - useful to know why the header was being ignored. System properties can be defined in the file "bin/system.properties" which is processed at startup, so should apply to the HTTP implementation. No code change needed; just edit the file. I'm not convinced that this should be the default. Note that the Java HTTP implementation has other failings; in general the Apache HttpClient implementation (3.1 currently, will also support 4.x in the next release) is much more flexible. Thanks for the clarification on the bin/system.properties, this is probably a good workaround. Is there a plan to switch to the Apache HttpClient for a future release? On further reflection, I think the setting -Dsun.net.http.allowRestrictedHeaders=true should be the default for JMeter. JMeter should be able to set such properties. URL: http://svn.apache.org/viewvc?rev=1125933&view=rev Log: Define sun.net.http.allowRestrictedHeaders=true by default. This fixes Bug 51238. Modified: jakarta/jmeter/trunk/bin/system.properties jakarta/jmeter/trunk/xdocs/changes.xml Thank you. This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2492 |