Front page returns 403 for unauthorized users

I’m trying to get a D7 staging site’s git repo up-to-date with its production server repo. In other words, I changed A LOT of stuff on staging (by running git fetch <branch> && git reset --hard). Now the site is up-t-date and works perfectly, except for one thing: to front page returns a 403 error for unauthenticated users.

My assumption is the error is in the .htaccess file. I did not overwrite it with the merge, though. Luckily I’m useless when it comes to handling .htaccess, and now have the opportunity to ask the smart folks on drupal stackexchange for their guidance.

The .htaccess file:

# # Apache/PHP/Drupal settings: #  # Protect files and directories from prying eyes. <FilesMatch ".(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(.php)?|xtmpl)(~|.sw[op]|.bak|.orig|.save)?$|^(..*|Entries.*|Repository|Root|Tag|Template)$|^#.*#$|.php(~|.sw[op]|.bak|.orig.save)$">   Order allow,deny </FilesMatch>  # Don't show directory listings for URLs which map to a directory. Options -Indexes  # Follow symbolic links in this directory. Options +FollowSymLinks  # Make Drupal handle any 404 errors. ErrorDocument 404 /index.php  # Set the default handler. DirectoryIndex index.php index.html index.htm  # Override PHP settings that cannot be changed at runtime. See # sites/default/default.settings.php and drupal_environment_initialize() in # includes/bootstrap.inc for settings that can be changed at runtime.  # PHP 5, Apache 1 and 2. <IfModule mod_php5.c>   php_flag magic_quotes_gpc                 off   php_flag magic_quotes_sybase              off   php_flag register_globals                 off   php_flag session.auto_start               off   php_value mbstring.http_input             pass   php_value mbstring.http_output            pass   php_flag mbstring.encoding_translation    off </IfModule>  # Requires mod_expires to be enabled. <IfModule mod_expires.c>   # Enable expirations.   ExpiresActive On    # Cache all files for 2 weeks after access (A).   ExpiresDefault A1209600    <FilesMatch .php$>     # Do not allow PHP scripts to be cached unless they explicitly send cache     # headers themselves. Otherwise all scripts would have to overwrite the     # headers set by mod_expires if they want another caching behavior. This may     # fail if an error occurs early in the bootstrap process, and it may cause     # problems if a non-Drupal PHP file is installed in a subdirectory.     ExpiresActive Off   </FilesMatch> </IfModule>  # Various rewrite rules. <IfModule mod_rewrite.c>   RewriteEngine on    # Set "protossl" to "s" if we were accessed via https://.  This is used later   # if you enable "www." stripping or enforcement, in order to ensure that   # you don't bounce between http and https.   RewriteRule ^ - [E=protossl]   RewriteCond %{HTTPS} on   RewriteRule ^ - [E=protossl:s]    # Make sure Authorization HTTP header is available to PHP   # even when running as CGI or FastCGI.   RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]    # Block access to "hidden" directories whose names begin with a period. This   # includes directories used by version control systems such as Subversion or   # Git to store control files. Files whose names begin with a period, as well   # as the control files used by CVS, are protected by the FilesMatch directive   # above.   #   # NOTE: This only works when mod_rewrite is loaded. Without mod_rewrite, it is   # not possible to block access to entire directories from .htaccess, because   # <DirectoryMatch> is not allowed here.   #   # If you do not have mod_rewrite installed, you should remove these   # directories from your webroot or otherwise protect them from being   # downloaded.   RewriteRule "(^|/)." - [F]    # If your site can be accessed both with and without the 'www.' prefix, you   # can use one of the following settings to redirect users to your preferred   # URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:   #   # To redirect all users to access the site WITH the 'www.' prefix,   # (http://example.com/... will be redirected to http://www.example.com/...)   # uncomment the following:   # RewriteCond %{HTTP_HOST} .   # RewriteCond %{HTTP_HOST} !^www. [NC]   # RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]   #   # To redirect all users to access the site WITHOUT the 'www.' prefix,   # (http://www.example.com/... will be redirected to http://example.com/...)   # uncomment the following:   # RewriteCond %{HTTP_HOST} ^www.(.+)$ [NC]   # RewriteRule ^ http%{ENV:protossl}://%1%{REQUEST_URI} [L,R=301]    # Modify the RewriteBase if you are using Drupal in a subdirectory or in a   # VirtualDocumentRoot and the rewrite rules are not working properly.   # For example if your site is at http://example.com/drupal uncomment and   # modify the following line:   # RewriteBase /drupal   #   # If your site is running in a VirtualDocumentRoot at http://example.com/,   # uncomment the following line:   # RewriteBase /    # Pass all requests not referring directly to files in the filesystem to   # index.php. Clean URLs are handled in drupal_environment_initialize().   RewriteCond %{REQUEST_FILENAME} !-f   RewriteCond %{REQUEST_FILENAME} !-d   RewriteCond %{REQUEST_URI} !=/favicon.ico   RewriteRule ^ index.php [L]    # Rules to correctly serve gzip compressed CSS and JS files.   # Requires both mod_rewrite and mod_headers to be enabled.   <IfModule mod_headers.c>     # Serve gzip compressed CSS files if they exist and the client accepts gzip.     RewriteCond %{HTTP:Accept-encoding} gzip     RewriteCond %{REQUEST_FILENAME}.gz -s     RewriteRule ^(.*).css $1.css.gz [QSA]      # Serve gzip compressed JS files if they exist and the client accepts gzip.     RewriteCond %{HTTP:Accept-encoding} gzip     RewriteCond %{REQUEST_FILENAME}.gz -s     RewriteRule ^(.*).js $1.js.gz [QSA]      # Serve correct content types, and prevent mod_deflate double gzip.     RewriteRule .css.gz$ - [T=text/css,E=no-gzip:1]     RewriteRule .js.gz$ - [T=text/javascript,E=no-gzip:1]      <FilesMatch "(.js.gz|.css.gz)$">       # Serve correct encoding type.       Header set Content-Encoding gzip       # Force proxies to cache gzipped & non-gzipped css/js files separately.       Header append Vary Accept-Encoding     </FilesMatch>   </IfModule> </IfModule>  # Add headers to all responses. <IfModule mod_headers.c>   # Disable content sniffing, since it's an attack vector.   Header always set X-Content-Type-Options nosniff </IfModule> 
Sponsored by SupremePR
This article was republished from its original source.
Call Us: 1(800)730-2416

Pixeldust is a 20-year-old web development agency specializing in Drupal and WordPress and working with clients all over the country. With our best in class capabilities, we work with small businesses and fortune 500 companies alike. Give us a call at 1(800)730-2416 and let’s talk about your project.

FREE Drupal SEO Audit

Test your site below to see which issues need to be fixed. We will fix them and optimize your Drupal site 100% for Google and Bing. (Allow 30-60 seconds to gather data.)

Powered by

Front page returns 403 for unauthorized users

On-Site Drupal SEO Master Setup

We make sure your site is 100% optimized (and stays that way) for the best SEO results.

With Pixeldust On-site (or On-page) SEO we make changes to your site’s structure and performance to make it easier for search engines to see and understand your site’s content. Search engines use algorithms to rank sites by degrees of relevance. Our on-site optimization ensures your site is configured to provide information in a way that meets Google and Bing standards for optimal indexing.

This service includes:

  • Pathauto install and configuration for SEO-friendly URLs.
  • Meta Tags install and configuration with dynamic tokens for meta titles and descriptions for all content types.
  • Install and fix all issues on the SEO checklist module.
  • Install and configure XML sitemap module and submit sitemaps.
  • Install and configure Google Analytics Module.
  • Install and configure Yoast.
  • Install and configure the Advanced Aggregation module to improve performance by minifying and merging CSS and JS.
  • Install and configure Schema.org Metatag.
  • Configure robots.txt.
  • Google Search Console setup snd configuration.
  • Find & Fix H1 tags.
  • Find and fix duplicate/missing meta descriptions.
  • Find and fix duplicate title tags.
  • Improve title, meta tags, and site descriptions.
  • Optimize images for better search engine optimization. Automate where possible.
  • Find and fix the missing alt and title tag for all images. Automate where possible.
  • The project takes 1 week to complete.