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
Describe the bug
When making a POST/PUT/non-GET request that returns a 302 redirect utilizing the Got http-client, Thunder Client will not rewrite the request as a GET, frequently causing a 404/error.
When performing the same with Axios, it does rewrite the request as GET. (Which is what the browser and most clients (postman, etc) do.)
To Reproduce
Using the Got http-client, make a request to a POST endpoint that returns a 302 redirect to a GET endpoint.
Request POST /logout and receive 404 instead of 200.
Expected behavior
By default, other clients (Postman, etc) will typically rewrite the request as GET (default Axios behavior), so you'd receive Hello! from the example above.
Would expect requests made with Got to follow this behavior.
It is the default behavior of Got NOT to do this per HTTP spec and their docs but it can be changed.
It looks like it was attempted to be addressed #388 but was not.
Seems like this could be resolved by setting the methodRewriting boolean to true.
Platform:
extension version: v2.33.2
Are you using the free version/paid version/trial:
Free
The text was updated successfully, but these errors were encountered:
Describe the bug
When making a POST/PUT/non-GET request that returns a 302 redirect utilizing the Got http-client, Thunder Client will not rewrite the request as a GET, frequently causing a 404/error.
When performing the same with Axios, it does rewrite the request as GET. (Which is what the browser and most clients (postman, etc) do.)
To Reproduce
Using the Got http-client, make a request to a POST endpoint that returns a 302 redirect to a GET endpoint.
Request POST
/logout
and receive 404 instead of 200.Expected behavior
By default, other clients (Postman, etc) will typically rewrite the request as GET (default Axios behavior), so you'd receive Hello! from the example above.
Would expect requests made with Got to follow this behavior.
It is the default behavior of Got NOT to do this per HTTP spec and their docs but it can be changed.
It looks like it was attempted to be addressed #388 but was not.
Seems like this could be resolved by setting the methodRewriting boolean to true.
Platform:
Are you using the free version/paid version/trial:
Free
The text was updated successfully, but these errors were encountered: