https://bz.apache.org/bugzilla/show_bug.cgi?id=62261

--- Comment #2 from Michael Osipov <1983-01...@gmx.net> ---
(In reply to Philippe Mouawad from comment #1)
> Hello,
> In last nightly build, I get the following:
> 
> First request:
> Connection: keep-alive
> Content-Type: 
> Content-Length: 0
> Host: localhost:8081
> User-Agent: Apache-HttpClient/4.5.5 (Java/1.8.0_161)
> 
> 
> Second Request:
> Connection: keep-alive
> Content-Type: 
> Content-Length: 41
> Host: localhost:8081
> User-Agent: Apache-HttpClient/4.5.5 (Java/1.8.0_161)

This is now consistent. Looks good.

> Would you expect that when Multipart form is checked it overrides parent set
> Header Content-Type ?

I would expect it from both, when the HTTP POST sets the context type,
regardless application/x-www-form-urlencoded or multipart/form-data.., it
deliberately overrides the conent type set by a parent. The problem with
application/x-www-form-urlencoded is that people do not see that it is set by
default. It should behave like a header manager for this thread group.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to