Technical Analysis and Solutions for HTTP to HTTPS Redirect Caching Issues in Firefox

Problem Symptoms and Background Analysis

During web development and server configuration, developers often encounter issues with browser-cached redirect rules. According to user reports, when accessing http://example.com in Firefox, the browser automatically redirects to https://example.com, even if the server is not configured for such redirection. This phenomenon does not occur in private browsing mode or other browsers (e.g., Chrome), indicating that the issue is related to Firefox's specific caching mechanisms.

Technical Principle Investigation

Firefox employs a multi-layered caching system to optimize user experience, including history, DNS cache, and site preferences. Site preferences are a persistent storage mechanism that records user access preferences for specific websites, such as forcing HTTPS usage. When the browser detects that a user has previously accessed a site via HTTPS, it may automatically upgrade HTTP requests to HTTPS in subsequent visits, even without explicit server requirements.

The core logic of this behavior can be illustrated with the following pseudocode example:

function checkRedirect(url) {
    let sitePreferences = getSitePreferences(url);
    if (sitePreferences.forceHTTPS) {
        return redirectToHTTPS(url);
    }
    return null;
}

In this code, the getSitePreferences function retrieves site preferences from the browser's persistent storage. If the forceHTTPS flag is set, a redirect is triggered. This mechanism aims to enhance security but can cause confusion during development and debugging.

Detailed Solutions

For different versions of Firefox, clearing site preferences is the key step to resolve this issue. Below are the specific operational guidelines:

Firefox 119.0 and Above

1. Open the Settings menu.
2. Type "clear history" in the search box.
3. Click the Clear History button.
4. Deselect the "Everything" option.
5. Select only the Site Settings option.
6. Click the Clear Now button.
7. Revisit the target website to verify if the issue is resolved.

Older Firefox Versions (e.g., from 2015)

1. Go to the Preferences menu.
2. Select the Privacy tab.
3. Click the "Clear Your History" link.
4. In the pop-up dialog, click the Details button.
5. Deselect all options, keeping only Site Preferences.
6. Select "Everything" from the top dropdown menu.
7. Click the OK button to complete the operation.

Supplementary Configuration Adjustments

If the issue persists after clearing site preferences, further adjustments to relevant parameters in about:config may be necessary. Key configuration items and their functions include:

• network.stricttransportsecurity.preloadlist: Setting this to false disables the HSTS preload list, which contains domains that enforce HTTPS.
• browser.fixup.fallback-to-https: Setting this to false prevents the browser from automatically falling back to HTTPS on connection failures.
• dom.security.https_first and dom.security.https_first_pbm: In Firefox 100 and above, setting these to false disables the HTTPS-first policy, including in private browsing mode.

When adjusting these parameters, note the potential impact on browser security. It is recommended to make temporary changes in development environments and use caution in production settings.

Troubleshooting and Verification

After implementing the above solutions, verify that the issue is fully resolved through the following steps:

1. Use the browser's developer tools network panel to monitor HTTP requests and confirm no abnormal redirects.
2. Send HTTP requests via command-line tools like curl to compare browser behavior.
3. Test in different browsers and private browsing modes to ensure the issue is specific to certain Firefox configurations.

If the problem persists, check for interference from browser extensions or system-level security software (e.g., Avast), as these tools can sometimes modify network request behavior.

Conclusion and Best Practices

HTTP to HTTPS redirect caching issues in Firefox typically stem from persistent storage of site preferences. By clearing these settings or adjusting related configuration parameters, developers can restore normal HTTP access behavior. During web development, it is advisable to regularly clear browser caches and cautiously modify parameters in about:config to avoid similar issues. Understanding the browser's internal redirect logic aids in more efficient debugging and troubleshooting.