Postman behavior with redirects
Some servers automatically redirect incoming calls to different
URLs. For example, a call that uses a non-secure URL (one starting with
http://
) may get automatically redirected to a secure URL (one starting
with https://
).
When Postman executes a POST or PATCH and is redirected to a new URL, Postman automatically changes the operation to a GET. This changes the outcome of the operation, as a GET will only retrieve data. This behavior can cause confusion during development, as the developer using Postman may not realize the POST or PATCH is being turned into a GET, or they may not realize why Postman is making the change.
You can avoid this behavior by ensuring that you use URLs in Postman that avoid any redirect behavior from the server.