That is the incorrect behaviour — only a 303 should cause a post to turn into a get. It seems that 302 was originally intended to be a temporary redirect, (like 307), but in practice, most browsers treated it like a 303 But what's the difference between a 303 and a 301 Is 301 supposed to mean the redirect is more permanent? If the 307/308 response code is not recognized, the form will be displayed to the user and the redirect will be able to be completed manually The temporary uri should be given by the location field in the response.
Asked 3 years, 10 months ago modified 1 year, 1 month ago viewed 69k times When upgrading my.net core 2.2 api to.net core 3.1, a lot of changes were required I had to update the swashbuckle package and change the startup file I now got it running in dev with swagger. I am wondering about the difference between 301 and 307 redirects The 307 (temporary redirect) status code indicates that the target resource resides temporarily under a different uri and the user agent must not change the request method if it performs an automatic redirection to that uri.
When i try and invoke my service locally in p. I found some useflul information in documentation about redirects with initial method saving Why does next.js use 307 and 308 Traditionally a 302 was used for a temporary redirect, and a 301 for a permanent redirect, but many browsers changed the request method of the redirect to get, regardless of the original method For example, if the browser made a request to post /v1/users which.
OPEN
