A temporary HTTP redirect that tells the client to repeat a request at another URL without changing its original method or request body.
Decision rule and boundaries
A temporary HTTP redirect that tells the client to repeat a request at another URL without changing its original method or request body. 307 is a temporary HTTP response. Unlike a 302, it requires the next request to retain the original method and body; that distinction matters for POST, PUT, PATCH, and DELETE, while a normal GET page usually needs a temporary redirect only for a genuinely temporary move.
How to inspect it
Inspect both the status and the Location header, then send a safe non-GET test request only to a controlled endpoint. A browser’s followed GET request cannot prove that a form or API body would be preserved.
Practical workflow
Keep a redirect map with owner and removal date. For a temporary API route, test the old method at the old route and the expected method at the new route before enabling traffic; for a permanent public-page move, choose a permanent redirect instead.
Common mistakes and measurement limits
A 307 is not an SEO migration switch. Search systems may keep the original URL because the response declares the change temporary; do not infer link or indexing effects from the code alone. The common failure mode is treating 307 as a permanent URL migration or assuming a header-only check proves method preservation.