What it means
The server directs the client to fetch another URL with GET, typically to show the result of a POST.
Common causes
- Post/Redirect/Get after a form submission
- An API pointing to the result of a long-running job
How to fix it
As a client or visitor
Issue a GET to Location. This prevents duplicate submissions when the user refreshes.
As the site or API owner
Use 303 after successful form POSTs to send users to a result page, so reloading does not resubmit the form.
Example response
HTTP/1.1
HTTP/1.1 303 See Other
Date: Tue, 07 Oct 2025 09:30:00 GMT
Server: nginx
Location: /orders/1001
Content-Length: 0Specification
FAQ
› What is the Post/Redirect/Get pattern?
After a POST the server returns 303 to a result page; the browser loads it with GET, so refresh and back are safe.
› 303 vs 302?
303 always means "GET the other URL". 302 does not specify the method, though browsers also switch to GET.