You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: