HTTP 307 Temporary Redirect
Like 302 but explicitly preserves the original HTTP method and body.
What it means
307 was introduced to fix the 302 method-conversion mess. A 307 redirect tells the client "the resource is temporarily at this other URL — keep using the same method." POST stays POST, PUT stays PUT, body is replayed.
Use 307 for API redirects where the client is doing a non-GET request. Use 308 if the move is permanent.
Common causes
- API route relocation that must preserve POST/PUT/PATCH
- Load balancer routing rules during traffic shaping
- Modern frameworks defaulting to 307 instead of 302
How to fix it
- 1If permanent, switch to 308 to capture SEO benefit
- 2Ensure the destination accepts the same HTTP method as the original request
How Uptimera reports 307
Uptimera follows 307 and reports the final status.
Related codes
Found
Temporary redirect. Resource is at a different URL right now but will be back at the original.
Permanent Redirect
Permanent version of 307. Method is preserved across the redirect, link equity transfers.
Moved Permanently
The resource has moved to a new URL permanently. Clients should update bookmarks; search engines transfer link equity.
Catch 307s before your customers do
Uptimera monitors your URLs from multiple regions and alerts the moment a 307 starts firing. Free plan included.