https://bz.apache.org/bugzilla/show_bug.cgi?id=60575
lpetr <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW --- Comment #21 from lpetr <[email protected]> --- Hello, As I explained in the ticket #60579 (which was linked to this issue as duplicate), since JMeter 3.1 "HTTP request" sampler adds unnecessary "Content-Type: text/plain; charset=ISO-8859-1" header into GET requests which has NO DATA in body. It could cause request rejection on FW, because it's considered malicious. RFC2616 section 7.2.1 says: "A Content-Type specifies the media type of the underlying data. A Content-Encoding may be used to indicate any additional content coding applied to the type, usually for the purpose of data compression, that is a property of the resource requested. The default for the content encoding is none (i.e., the identity function)." If my understanding is correct, the header "Content-Type" should not be present for simple GET requests without "entity-body", because there are no "underlying data". Here are GET requests to google for simple comparison of JMeter 3.0 and JMeter 3.1 behavior: ------ Behavior of the JMeter 3.0 HTTP Sampler (NO content type and length header - expected): ------ GET https://google.com/ [no cookies] Request Headers: Connection: keep-alive Host: google.com User-Agent: Apache-HttpClient/4.5.2 (Java/1.8.0_111) ----- Behavior of the JMeter 3.1 HTTP Sampler (Content type header send - possible problem): ----- GET http://www.google.com/ GET data: [no cookies] Request Headers: Connection: keep-alive Content-Length: 0 Content-Type: text/plain; charset=ISO-8859-1 Host: www.google.com User-Agent: Apache-HttpClient/4.5.2 (Java/1.8.0_111) -- You are receiving this mail because: You are the assignee for the bug.
