Content-Type header removed for POST with empty (0 length) payload starting in v3.10.2
Blackbaud-ChrisBlythe opened this issue · comments
Starting in v3.10.2, we have found that Gatling is removing our explicitly defined Content-Type headers on POST requests that have an empty (0 length) payload.
We have confirmed that v3.10.1 (and all previous versions we've used over the years) preserves the Content-Type header in this situation, while v3.10.2 and v3.10.3 both remove the header.
Discussed on community: https://community.gatling.io/t/after-upgrade-to-3-10-3-header-with-content-type-was-omitted-at-request/8607
Already fixed in #4509
Waiting for a new release to ship
THX!
Hello @slandelle
When do you plan to deploy 3.10.4 version?
Next week