302 Status Code: What It Means and What to Do

A 302 status code is a temporary redirect: the server is telling your browser that the page you asked for lives at a different address for now. The original address stays the real one, which is the whole difference between a 302 and a permanent redirect.

You normally never see a 302 because the browser follows it in a fraction of a second and shows you the destination page. A 302 becomes visible when something goes wrong — a login that bounces back to the sign-in screen, a tool that reports the code instead of following it, or a redirect chain that never ends.

What does a 302 status code actually mean?

A web status code is a three-digit number a server sends with every response, telling the browser what happened. Codes in the 300s are redirects: the answer is not here, look somewhere else. A 302 in that family means "found, but at another address, temporarily."

Along with the code, the server sends a location header naming the address to go to. The browser reads that header and requests the new address automatically. If the location header is missing or points at nonsense, the browser has nowhere to go and you see an error instead of a page.

Where do people run into a 302 status code?

• Signing in. A site takes your credentials, then redirects you to the page you originally wanted. That redirect is usually a 302.
• Session expiry. A page you were reading redirects you back to a login screen because the session timed out.
• Maintenance. A site sends everyone to a notice page while work is under way, and uses a temporary redirect so the original addresses keep their standing.
• Region or language handling. A request gets sent to a country or language version of the same page.
• Short links and tracking links. Many of them answer with a temporary redirect to the real destination.

How is a 302 different from a 301, 307, and 308?

All four are redirects. They differ in whether the move is permanent and in whether the request method is allowed to change:

• 301 — permanent. The address has moved for good; clients and search engines are expected to remember the new one.
• 302 — temporary. The original address is still the canonical one and should not be replaced in anyone's records.
• 307 — temporary, and strict about the method. A form submission stays a form submission at the new address.
• 308 — permanent, and strict about the method in the same way.

The method question matters more than it sounds. Historically, browsers handling a 302 after a form submission would turn it into a plain page request, dropping the submitted data. That behavior is why 307 exists. If you are redirecting after a form submission and the data disappears, the redirect code is the first thing to check.

Why does my login page keep redirecting and never sign me in?

A login loop is a 302 sending you back where you came from, over and over. Work through this order:

1. Check the clock on your device. A device with the wrong date can reject the session cookie the moment it arrives, and the site then redirects you back to sign in.
2. Allow cookies for the site, including third-party cookies if the sign-in happens on a different domain than the app. A blocked cookie means the site never sees that you signed in.
3. Clear the cookies for that site specifically, then sign in once, cleanly. A stale session cookie from an earlier attempt causes exactly this loop.
4. Turn off tracking-protection extensions and any VPN for one attempt. Both can break the hop between the sign-in domain and the application domain.
5. Try a private window, and then a different browser. If the loop happens in one browser only, the problem is local data, not the site.
6. If it loops in every browser and on mobile data as well, the problem is on the site's side and there is nothing to fix from your end.

What causes a 302 redirect loop?

A loop happens when address A redirects to B and B redirects back to A. Browsers stop after a set number of hops and show a "too many redirects" error rather than looping forever. Common causes are a rule that redirects to a secure address combined with a proxy that keeps reporting the request as insecure, a country-detection rule that disagrees with itself, and an authentication check that redirects to a login page which itself requires authentication.

Should a 302 be used for a page that moved permanently?

No. If the move is permanent, use a permanent redirect. A temporary redirect tells everything downstream to keep the old address, which means caches, bookmarks, and search engines keep pointing at an address you no longer want used. Temporary redirects left in place for months are one of the more common quiet mistakes on a site, because nothing breaks visibly — pages still load, they simply keep the wrong address in everyone's records.

How do I see the 302 status code for myself?

1. Open your browser's developer tools and select the network panel.
2. Enable the option to preserve the log across navigations, otherwise the redirect scrolls away when the destination page loads.
3. Reload the page and look at the first request in the list. Its status column shows the code, and the response headers show the location header naming the destination.
4. Follow the chain down the list. Every hop is a separate row, so you can see exactly where a loop starts.

Does a 302 status code mean something is broken?

Usually not. A 302 is a normal part of signing in, of short links, and of maintenance windows, and it is invisible when everything works. Treat it as a problem in three cases: when the redirect never resolves and you get a loop error, when a permanent move is being served as temporary, and when a form submission loses its data on the way through the redirect. Everything else is the code doing its job.