HTTP 302 Found
Temporary redirect. Resource is at a different URL right now but will be back at the original.
What it means
302 indicates a temporary redirect — "the resource is over there for now, but check this URL again next time." Browsers honor it but don't update bookmarks. Search engines do not transfer link equity (or transfer much less than 301).
Common gotcha: 302 historically had ambiguous semantics around whether to preserve the HTTP method on the redirect. Many clients convert POST → GET on 302, which is rarely what you want for APIs. Use 307 (preserves method) or 308 (permanent + preserves method) for API redirects.
Common causes
- Maintenance redirect to a temporary page
- Authentication flow that bounces unauthenticated users to a login URL
- Geo-routing for users in a specific region
- Default redirect verb from many web frameworks
How to fix it
- 1If the move is permanent, switch to 301 to preserve SEO link equity
- 2If method preservation matters (POST/PUT/PATCH/DELETE), switch to 307 or 308
- 3Check the Location header is valid and reachable
How Uptimera reports 302
Uptimera follows 302 and reports the final response status by default.
Catch 302s before your customers do
Uptimera monitors your URLs from multiple regions and alerts the moment a 302 starts firing. Free plan included.