TYPO3 6.2 HTTPS迁移遇301无限重定向循环问题咨询

Hey there, let's break down why you're hitting that frustrating infinite 301 redirect loop after tweaking settings for your TYPO3 6.2 HTTPS migration. Based on your current working config (config.absRefPrefix = auto, TCAdefaults.pages.url_scheme = 2), here are the most likely reasons modifying specific parameters triggers loops:

Common Culprits & Explanations #

1. Mismatched config.baseURL Configuration #

If you modified config.baseURL to use an HTTP protocol (e.g., http://yourdomain.com/) instead of HTTPS, this creates a direct conflict with your TCAdefaults.pages.url_scheme = 2 setting (which forces all pages to use HTTPS). Here's the cycle:

• TYPO3 generates internal links using the HTTP baseURL
• Your server (or TYPO3's own redirect logic) catches those HTTP links and redirects users to HTTPS
• When the HTTPS page loads, TYPO3 still outputs HTTP links from the misconfigured baseURL
• This repeats indefinitely, causing the loop

Even protocol-relative values like //yourdomain.com/ can cause issues if TYPO3 fails to detect the current request's HTTPS status.

2. Incorrect config.absRefPrefix Modification #

Moving away from config.absRefPrefix = auto to a hardcoded value breaks things if it doesn't align with your HTTPS setup:

• Setting it to an HTTP prefix (e.g., http://yourdomain.com/) triggers the same loop scenario as a misconfigured baseURL
• Setting it to an HTTPS prefix but having TYPO3 fail to recognize the current request is over HTTPS (often due to reverse proxies/load balancers) leads to TYPO3 generating HTTPS links for an HTTP-requested page, creating a redirect loop

3. Conflicting config.url_scheme Settings #

If you modified the root TypoScript config.url_scheme (not the TSconfig TCAdefaults.pages.url_scheme), a mismatch here creates chaos:

• Setting config.url_scheme = 1 (force HTTP) while TCAdefaults.pages.url_scheme = 2 (force HTTPS) pits TYPO3's link generation against page-level HTTPS enforcement, triggering back-and-forth redirects
• Even setting config.url_scheme = 0 (auto-detect) can cause loops if TYPO3 can't correctly identify the request protocol (common with reverse proxies)

4. Server Rewrite Rule Conflicts #

Don't overlook your server's HTTPS enforcement rules (in .htaccess for Apache, or Nginx config blocks). If your server forces all traffic to HTTPS but you modified a TYPO3 setting that generates HTTP links, you'll get stuck in a loop. The same goes if your server accidentally forces HTTP while TYPO3 pushes HTTPS.

Quick Troubleshooting Steps #

• Verify protocol consistency: Ensure config.baseURL (if set) uses https:// to match TCAdefaults.pages.url_scheme = 2
• Check HTTPS detection: Add a quick debug snippet to a test template to see if TYPO3 recognizes HTTPS:

  <?php echo isset($_SERVER['HTTPS']) ? $_SERVER['HTTPS'] : 'Not detected'; ?>
  

  If it returns "Not detected", configure TYPO3's reverse proxy settings in LocalConfiguration.php:

  $GLOBALS['TYPO3_CONF_VARS']['SYS']['reverseProxyIP'] = 'your-proxy-ip';
  $GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern'] = 'yourdomain\\.com';
  

• Isolate server rules: Temporarily disable your server's HTTPS redirect rules to see if the loop stops. If it does, adjust the rules to align with your TYPO3 config.
• Revert incrementally: Roll back your parameter changes one by one to identify exactly which setting is triggering the loop.

内容的提问来源于stack exchange，提问作者Paolito75