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
In my back end application under test, there is one (and only) GET request that started failing with the new 2.33.0 (and 2.33.1) version of WireMock. The exception is "javax.ws.rs.NotSupportedException: HTTP 415 Unsupported Media Type".
I assume this happens because of this change in 2.33.0:
Proxy will now send a request body for any request method (i assume this is proxy request fix #1765 ?)
I don't think this is right default behavior. When I didn't have a request entity the proxy shouldn't just add it for no reason.
Would it be a decent solution would be to check if the content length is 0 before adding the entity?
The text was updated successfully, but these errors were encountered:
I am using WireMock together with ChromeDriver - wiremock is instantiated and passed as a proxy to the ChromeDriver.
Here is how wiremock is instantiated:
On the chromedriver I just add the capabilities:
In my back end application under test, there is one (and only) GET request that started failing with the new 2.33.0 (and 2.33.1) version of WireMock. The exception is "javax.ws.rs.NotSupportedException: HTTP 415 Unsupported Media Type".
I assume this happens because of this change in 2.33.0:
I don't think this is right default behavior. When I didn't have a request entity the proxy shouldn't just add it for no reason.
Would it be a decent solution would be to check if the content length is 0 before adding the entity?
The text was updated successfully, but these errors were encountered: