302 Found HTTP Status Code


HTTP status code 302 is used to indicate that the resource requested has been temporarily moved to a different URI. This status code is part of the HTTP (Hypertext Transfer Protocol) response status codes that are issued by a server in response to a client's request made to the server.

When a web server responds with a 302 status code, it also provides a Location header in the response. This Location header contains the URL to which the request is redirected. Clients, such as web browsers, are expected to follow this redirection by making a new request to the URL specified in the Location header.

The 302 status code is commonly used in web applications to redirect users to a new location for various reasons, such as after a form submission where the user is redirected to a confirmation or thank you page, or when content has been moved to a new URL but the change is expected to be temporary.

It's important to note that when responding with a 302 status code, the method used for the subsequent request to the new location should be the same as the original request method. For example, if the original request was a GET, the client should use a GET request for the new URL provided in the Location header.

The main difference between HTTP status codes 302 and 301 (Moved Permanently) is that 302 indicates a temporary redirection, whereas 301 indicates that the resource has been moved to a new location permanently. This distinction is important for search engines and caching mechanisms, as they treat these two status codes differently in terms of indexing and caching behavior.


302 Found

Common Causes

Here are the primary causes or scenarios where a 302 status code might be used:

  1. Resource Moved Temporarily: The most straightforward cause for a 302 status code is when a resource or page has been moved to a new location temporarily, and the server wants to redirect the client to this new location for the time being. This could be due to maintenance, restructuring, or temporary content changes.

  2. Load Balancing: Sometimes, a 302 redirect might be used for load balancing purposes. Websites with heavy traffic might redirect users to different servers to distribute the load evenly. These redirects are temporary, as the balancing logic might change based on current server load.

  3. A/B Testing: In A/B testing, where two versions of a page are tested to see which one performs better, a 302 redirect might be used to temporarily send some users to the new version of the page while keeping the original page active for others.

  4. Geolocation and Language Redirection: Websites that offer content in multiple languages or tailored content based on the user's location might use a 302 redirect to send the user to the version of the site that best fits their locale or language preference, based on IP address or browser settings.

  5. Handling Form Submissions: Sometimes, after submitting a form on a website, a 302 redirect might be used to redirect the user to a new page to confirm that the submission was successful. This is to prevent form resubmission if the page is refreshed.

  6. Temporary Content Replacement: If a webpage is temporarily replaced with a special announcement or a promotional page, a 302 redirect might be used. Once the event is over, the redirect can be removed, and users will go back to the original content.

  7. URL Shortening Services: URL shorteners work by issuing a 302 redirect to the user's browser, redirecting it to the long URL that the short URL represents. This is inherently a temporary measure as the destination URL is maintained by the service.

  8. Enforcing HTTPS: Websites moving from HTTP to HTTPS might temporarily use 302 redirects to send users to the secure version of the site while they test and ensure everything works correctly before implementing a permanent redirect (301).

It's important to use 302 redirects appropriately, as improper use can lead to SEO issues, confusion for users, and potential security vulnerabilities. For permanent moves, a 301 status code is generally recommended.

Browser Support

The following table will show you the current browser support for the 302 Found HTTP status code.

Edge Chrome Firefox Opera Safari
Tablets / Mobile
Chrome Firefox Opera Safari Samsung Webview

Last updated by CSSPortal on: 31st March 2024