That is the incorrect behaviour — only a 303 should cause a post to turn into a get. I've created a.net core web api using the following command It seems that 302 was originally intended to be a temporary redirect, (like 307), but in practice, most browsers treated it like a 303
Queen Bee Chapter 307 Spoiler, Release Date, Raw Scan, Time, Where to
But what's the difference between a 303 and a 301
Is 301 supposed to mean the redirect is more permanent?
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. I am wondering about the difference between 301 and 307 redirects Asked 3 years, 11 months ago modified 1 year, 2 months ago viewed 69k times 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. It's an internal redirect, something that your browser does for you before even sending the request to the server That's why it won't show up in curl It's a feature of your browser
Curl is much more reliable when it comes to sending unaltered requests
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.
