307 Temporary Redirect

307 Temporary Redirect in TYPO3

The 307 Temporary Redirect is like a 302 redirect but is stricter, keeping the same HTTP request method. For example, if a user sends a POST request, a 307 redirect ensures the redirected page still uses POST rather than switching to GET. In TYPO3, 307 redirects are rarely needed but useful for temporary redirections that need to keep the request method intact.

Suggestions for 307 Temporary Redirect in TYPO3:

• Use for short-term redirections when keeping the HTTP method matters.
• Typically, this is more applicable for complex form submissions or APIs.
• Ensure it’s replaced with a 301 if the change becomes permanent.

Status code 307 tells browsers and search engines that a page is temporarily available at another address. Unlike 302, the original request method is preserved: a POST form is therefore not converted into a GET request. That makes 307 the safe choice when data is submitted and nothing may get lost.

Typical use cases are maintenance work, seasonal campaign pages or tests of a new page structure. The original URL keeps its ranking because search engines assume the redirect is not permanent. In TYPO3 you set up 307 redirects in the backend module “Redirects” and select the desired status code there.

Do not forget to review temporary redirects later. If a 307 stays active permanently, it sends misleading signals and can cause search engines to assign the target incorrectly. Once the new address becomes final, switch to a 301 or 308 redirect.

For search engines and users, a clear separation between temporary and permanent matters. Document in your editorial process which redirects are time-limited and enter a review date. That way temporary solutions do not sit unnoticed in the system for years and slow down neither loading time nor the overview in the redirect module.

In short: TYPO3 307 Temporary Redirect: Causes, Use Cases & Fixes.