HTTP 302 Found

3xx Redirection

3xx Redirection RFC 7231, Section 6.4.3

What is HTTP 302 Found?

The 302 (Found) status code indicates that the target resource resides temporarily under a different URI. The client should continue to use the original URI for future requests. Unlike 301, this redirect is temporary and search engines will keep indexing the original URL. In HTTP/1.0, this was the original temporary redirect and browsers implement it as a GET redirect regardless of the original request method.

Common Use Cases

Temporary page maintenance
A/B testing redirects
Post-login redirect
Campaign tracking redirects

Usage Example

After a user successfully logs in, redirect them to their dashboard using 302 Found. The browser navigates to the dashboard, but bookmarks and search engines retain the original URL. For A/B testing, 302 redirects let you send users to variant pages while test groups explore the original.

// Laravel - post-login redirect (302 by default)
return redirect()->intended('/dashboard');

// Express.js
res.redirect(302, '/temporary-page');

Related Status Codes

301 Moved Permanently 303 See Other 307 Temporary Redirect

Common Mistakes

⚠️

Mistake: Using 302 for permanent URL changes

Fix: If a URL change is permanent (e.g., domain migration, permalink change), use 301 Moved Permanently. Search engines will not transfer SEO value with 302 redirects.

⚠️

Mistake: Relying on 302 to preserve POST method

Fix: Most browsers change POST to GET when following a 302 redirect. If you need to preserve the HTTP method during a redirect, use 307 Temporary Redirect instead.

All 3xx Codes All Status Codes

Last updated: 21 Jun 2026

Blog