HTTPS强制访问下主站正常，子目录博客配置失效求助

Hey there! Let's figure out why your /blog subdirectory is misbehaving when accessed over HTTPS, even though your main site works perfectly. Here are the most common causes and fixes to try:

1. Check for a separate .htaccess in the /blog directory #

This is by far the most frequent culprit. Subdirectories often have their own .htaccess files that can override or conflict with the main site's HTTPS rules. For example:

• The /blog/.htaccess might contain rules that force HTTP instead of HTTPS
• It could have rewrite rules that reference hardcoded HTTP URLs
• Or it might disable mod_rewrite entirely, breaking the main site's redirects

Fix: Navigate to your /blog directory and look for a .htaccess file. If it exists:

• Open it and scan for any rules mentioning HTTPS off or HTTP-specific URLs
• Remove or modify conflicting rules (e.g., replace HTTP references with HTTPS, delete forced HTTP redirects)
• If the subdirectory doesn't need its own .htaccess, rename it temporarily (like .htaccess-old) to test if the main site's rules start working for /blog

2. Verify your main .htaccess HTTPS rules apply to subdirectories #

Make sure your main site's HTTPS enforcement rule covers all subdirectories, not just the root. A correct, universal HTTPS redirect rule looks like this:

RewriteEngine On
# Force HTTPS for all requests
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

• The ^(.*)$ pattern ensures every path (including /blog and its subpages) gets redirected
• The [L,R=301] flags mark the redirect as permanent and stop further rule processing

If your existing rule uses a restrictive pattern (like ^$ for the root only), that's why /blog isn't getting the HTTPS treatment.

3. Check Apache Virtual Host configuration for HTTPS #

Sometimes the issue lies in your Apache server's virtual host setup for HTTPS:

• Ensure your HTTPS <VirtualHost> block uses the same DocumentRoot as your HTTP block (pointing to your main site's root directory)
• Make sure there's no separate <Location /blog> block in the HTTPS config overriding settings (like disabling rewrites or forcing HTTP)
• Confirm your SSL certificate is valid for the entire domain (subdirectories don't need separate certificates unless you're using subdomains, which you aren't here)

Fix: Locate your Apache sites configuration (usually in /etc/apache2/sites-available/ on Linux) and compare the HTTP and HTTPS virtual host blocks for inconsistencies.

4. Clear browser cache (it's easier than you think!) #

Old cached redirects or HTTP resources can cause weird behavior when switching to HTTPS. Try accessing your blog's HTTPS URL in incognito/private mode first—if it works, your regular browser cache is holding onto outdated data. Clear your cache and cookies to fix this.

5. Double-check mod_rewrite is enabled #

While your main site works, it's worth confirming the rewrite module is active for the entire server. Run these commands on your server:

sudo a2enmod rewrite
sudo systemctl restart apache2

This ensures mod_rewrite is enabled and Apache picks up the change.

Start with checking for a separate .htaccess in /blog—that's almost always the issue. If none of these steps work, feel free to share snippets of your main and /blog .htaccess files, and I can help dig deeper!

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