.htaccess corruption

Hi Paul,

Yes, we are using the function to rename the login.

The only other security plugin we have is Wordfence. But I can give you a complete list of plugins if that would help.

Is there somewhere that I could send the 2 .htaccess files to you. I don’t want to post them here.

Thank you for looking into this and making the new version.

Hi,

Here is what is in the bad file with a lot of spaces in front of this on the line:

Redirect permanent /v
ancouverlistings/realestate/sold/item/225 http://www.domain.ca/condo/803-1033-marinaside-crescent-quaywest-1-yaletown-condo-vancouver-west

this is what it should have had in the file:

Redirect permanent /first-time-home-buyers-guide-episode-5-comparative-market-analysis-for-buyers-–-what’s-your-dream-home-worth http://www.domain.ca/first-time-home-buyers-guide-episode-5-comparative-market-analysis-for-buyers-whats-your-dream-home-worth
Redirect permanent /proximity-vancouver-by-bastion-new-condo-presale-in-olympic-village-floor-plans-pricing-to-come http://www.domain.ca/proximity-a-sleek-and-sustainable-new-condo-development-near-olympic-village
Redirect permanent /first-time-home-buyers-guide-vancouver-–-episode-2-–-where-to-buy http://www.domain.ca/first-time-home-buyers-guide-vancouver-episode-2-where-to-buy
Redirect permanent /bennington-house-townhouses-on-the-cambie-corridor-pricing-floor-plans-to-come http://www.domain.ca/bennington-house-presale-condos-townhouses-on-the-cambie-corridor-floor-plans-pricing-to-come
Redirect permanent /aperture-vancouver-new-condo-on-the-cambie-corridor-with-pricing-floor-plans http://www.domain.ca/aperture-an-architectural-marvel-along-vancouvers-fast-growing-cambie-corridor
Redirect permanent /the-wohlsein-vancouver-presale-condo-with-floor-plans-pricing-to-come http://www.domain.ca/the-wohlsein-vancouver-presale-condo-with-floor-plans-pricing
Redirect permanent /for-buyers/vancouver-condo-pre-sales/west-side-presale-condos http://www.domain.ca/for-buyers/vancouver-condo-pre-sales/west-side-presale

# LISTINGS (OLD JOOMLA SITE)

#Root of listings redirected manually with HTML file; this not needed:
#Redirect permanent /vancouverlistings http://www.domain.ca

Redirect permanent /vancouverlistings/sitemap http://www.domain.ca/sitemap

# Key Listings by ID

Redirect permanent /vancouverlistings/item/225 http://www.domain.ca/condo/803-1033-marinaside-crescent-quaywest-1-yaletown-condo-vancouver-west
Redirect permanent /vancouverlistings/realestate/featured-listings/item/225 http://www.domain.ca/condo/803-1033-marinaside-crescent-quaywest-1-yaletown-condo-vancouver-west
Redirect permanent /vancouverlistings/realestate/sold/item/225 http://www.domain.ca/condo/803-1033-marinaside-crescent-quaywest-1-yaletown-condo-vancouver-west

This is what is in the file before the bad code:

#WFIPBLOCKS - Do not remove this line. Disable Web Caching in Wordfence to remove this data.
Order Deny,Allow
#Do not remove this line. Disable Web Caching in Wordfence to remove this data - WFIPBLOCKS
#WFCACHECODE - Do not remove this line. Disable Web Caching in Wordfence to remove this data.
<IfModule mod_deflate.c>
	AddOutputFilterByType DEFLATE text/css text/x-component application/x-javascript application/javascript text/javascript text/x-js text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon application/json
	<IfModule mod_headers.c>
		Header append Vary User-Agent env=!dont-vary
	</IfModule>
	<IfModule mod_mime.c>
		AddOutputFilter DEFLATE js css htm html xml
	</IfModule>
</IfModule>
<IfModule mod_mime.c>
	AddType text/html .html_gzip
	AddEncoding gzip .html_gzip
	AddType text/xml .xml_gzip
	AddEncoding gzip .xml_gzip
</IfModule>
<IfModule mod_setenvif.c>
	SetEnvIfNoCase Request_URI \.html_gzip$ no-gzip
	SetEnvIfNoCase Request_URI \.xml_gzip$ no-gzip
</IfModule>
<IfModule mod_headers.c>
	Header set Vary "Accept-Encoding, Cookie"
</IfModule>
<IfModule mod_rewrite.c>
	#Prevents garbled chars in cached files if there is no default charset.
	AddDefaultCharset utf-8

	#Cache rules:
	RewriteEngine On
	RewriteBase /
	RewriteCond %{HTTPS} on
	RewriteRule .* - [E=WRDFNC_HTTPS:_https]
	RewriteCond %{HTTP:Accept-Encoding} gzip
	RewriteRule .* - [E=WRDFNC_ENC:_gzip]
	RewriteCond %{REQUEST_METHOD} !=POST
	RewriteCond %{HTTPS} off
	RewriteCond %{QUERY_STRING} ^(?:\d+=\d+)?$
	RewriteCond %{REQUEST_URI} (?:\/|\.html)$ [NC]

	RewriteCond %{HTTP_COOKIE} !(comment_author|wp\-postpass|wf_logout|wordpress_logged_in|wptouch_switch_toggle|wpmp_switcher) [NC]

	RewriteCond %{REQUEST_URI} \/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)(.*)$
	RewriteCond "%{DOCUMENT_ROOT}/wp-content/wfcache/%{HTTP_HOST}_%1/%2~%3~%4~%5~%6_wfcache%{ENV:WRDFNC_HTTPS}.html%{ENV:WRDFNC_ENC}" -f
	RewriteRule \/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)(.*)$ "/wp-content/wfcache/%{HTTP_HOST}_$1/$2~$3~$4~$5~$6_wfcache%{ENV:WRDFNC_HTTPS}.html%{ENV:WRDFNC_ENC}" [L]
</IfModule>
#Do not remove this line. Disable Web caching in Wordfence to remove this data - WFCACHECODE
# BEGIN HTML5 Boilerplate
# ----------------------------------------------------------------------
# Proper MIME type for all files
# ----------------------------------------------------------------------
# JavaScript
#   Normalize to standard type (it's sniffed in IE anyways)
#   tools.ietf.org/html/rfc4329#section-7.2
AddType application/javascript         js jsonp
AddType application/json               json
# Audio
AddType audio/ogg                      oga ogg
AddType audio/mp4                      m4a f4a f4b
# Video
AddType video/ogg                      ogv
AddType video/mp4                      mp4 m4v f4v f4p
AddType video/webm                     webm
AddType video/x-flv                    flv
# SVG
#   Required for svg webfonts on iPad
#   twitter.com/FontSquirrel/status/14855840545
AddType     image/svg+xml              svg svgz
AddEncoding gzip                       svgz
# Webfonts
AddType application/vnd.ms-fontobject  eot
AddType application/x-font-ttf         ttf ttc
AddType font/opentype                  otf
AddType application/x-font-woff        woff
# Assorted types
AddType image/x-icon                        ico
AddType image/webp                          webp
AddType text/cache-manifest                 appcache manifest
AddType text/x-component                    htc
AddType application/xml                     rss atom xml rdf
AddType application/x-chrome-extension      crx
AddType application/x-opera-extension       oex
AddType application/x-xpinstall             xpi
AddType application/octet-stream            safariextz
AddType application/x-web-app-manifest+json webapp
AddType text/x-vcard                        vcf
AddType application/x-shockwave-flash       swf

# ----------------------------------------------------------------------
# Expires headers (for better cache control)
# ----------------------------------------------------------------------
# These are pretty far-future expires headers.
# They assume you control versioning with filename-based cache busting
# Additionally, consider that outdated proxies may miscache
#   www.stevesouders.com/blog/2008/08/23/revving-filenames-dont-use-querystring/
# If you don't use filenames to version, lower the CSS  and JS to something like
#   "access plus 1 week" or so.
 <IfModule mod_expires.c>
   ExpiresActive on
# Perhaps better to whitelist expires rules? Perhaps.
   ExpiresDefault                          "access plus 1 month"
# cache.appcache needs re-requests in FF 3.6 (thanks Remy ~Introducing HTML5)
   ExpiresByType text/cache-manifest       "access plus 0 seconds"
# Your document html
   ExpiresByType text/html                 "access plus 0 seconds"
# Data
   ExpiresByType text/xml                  "access plus 0 seconds"
   ExpiresByType application/xml           "access plus 0 seconds"
   ExpiresByType application/json          "access plus 0 seconds"
# Feed
   ExpiresByType application/rss+xml       "access plus 1 hour"
   ExpiresByType application/atom+xml      "access plus 1 hour"
# Favicon (cannot be renamed)
   ExpiresByType image/x-icon              "access plus 1 week"
# Media: images, video, audio
   ExpiresByType image/gif                 "access plus 1 month"
   ExpiresByType image/png                 "access plus 1 month"
   ExpiresByType image/jpg                 "access plus 1 month"
   ExpiresByType image/jpeg                "access plus 1 month"
   ExpiresByType video/ogg                 "access plus 1 month"
   ExpiresByType audio/ogg                 "access plus 1 month"
   ExpiresByType video/mp4                 "access plus 1 month"
   ExpiresByType video/webm                "access plus 1 month"
# HTC files  (css3pie)
   ExpiresByType text/x-component          "access plus 1 month"
# Webfonts
   ExpiresByType application/x-font-ttf    "access plus 1 month"
   ExpiresByType font/opentype             "access plus 1 month"
   ExpiresByType application/x-font-woff   "access plus 1 month"
   ExpiresByType image/svg+xml             "access plus 1 month"
   ExpiresByType application/vnd.ms-fontobject "access plus 1 month"
# CSS and JavaScript
   ExpiresByType text/css                  "access plus 1 year"
   ExpiresByType application/javascript    "access plus 1 year"
 </IfModule>
# ----------------------------------------------------------------------
# ETag removal
# ----------------------------------------------------------------------
# FileETag None is not enough for every server.
# <IfModule mod_headers.c>
#   Header unset ETag
# </IfModule>
# Since we're sending far-future expires, we don't need ETags for
# static content.
#   developer.yahoo.com/performance/rules.html#etags
# FileETag None

Options -Indexes
# Block access to "hidden" directories or files whose names begin with a period. This
# includes directories used by version control systems such as Subversion or Git.
<IfModule mod_rewrite.c>
RewriteCond %{SCRIPT_FILENAME} -d [OR]
RewriteCond %{SCRIPT_FILENAME} -f
RewriteRule "(^|/)\." - [F]
</IfModule>
# Block access to backup and source files
# This files may be left by some text/html editors and
# pose a great security danger, when someone can access them
<FilesMatch "(\.(bak|config|sql|fla|psd|ini|log|sh|inc|swp|dist)|~)$">
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>
# Block access to WordPress files that reveal version information.
<FilesMatch "^(wp-config\.php|readme\.html|license\.txt)">
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>
<Files "xml-sitemap-xsl.php">
Allow from all
</Files>
# END HTML5 Boilerplate

RewriteCond %{HTTP_HOST} !^www\.domain\.ca$ [NC]
RewriteRule ^(.*)$ http://www.domain.ca/$1 [L,R=301]

#2015 Wildcard Redirects

#Replace spaces with hyphens and redirect tags
RewriteRule ^vancouverlistings/realestate/featured-listings/itemlist/tag/(.*)$ /content/fix_tag_urls.php [L]
RewriteRule ^vancouverlistings/realestate/sold/itemlist/tag/(.*)$ /content/fix_tag_urls.php [L]
RewriteRule ^vancouverlistings/component/k2/itemlist/tag/(.*)$ /content/fix_tag_urls.php [L]
RewriteRule ^vancouverlistings/itemlist/tag/(.*)$ /content/fix_tag_urls.php [L] 

# Replace /vancouverlistings/item/*-xxxxxxx remove *-
#RewriteRule ^vancouverlistings/item/([0-9]+)\-(.*)$ http://www.domain.ca/condo/$2 [NC,L,R=301]
#RewriteRule ^vancouverlistings/realestate/featured-listings/item/([0-9]+)\-(.*)$ http://www.domain.ca/condo/$2 [NC,L,R=301]
#RewriteRule ^vancouverlistings/realestate/sold/item/([0-9]+)\-(.*)$ http://www.domain.ca/condo/$2 [NC,L,R=301]
RewriteRule ^vancouverlistings/item/([0-9]+)\-(.*)$ /content/fix_urls.php [L]
RewriteRule ^vancouverlistings/realestate/sold/item/([0-9]+)\-(.*)$ /content/fix_urls.php [L]
RewriteRule ^vancouverlistings/realestate/featured-listings/item/([0-9]+)\-(.*)$ /content/fix_urls.php [L]

RewriteRule ^listing_details.php$ http://www.domain.ca/condos/? [R=301,L]
RewriteRule ^vancouverlistings/itemlist/$ http://www.domain.ca/condos/? [R=301,L]

# END of Wildcard redirects

# BEGIN Change backend login URL - NOT USED - Done by the firewall now
#RewriteRule ^manage/(.*) wp-admin/$1?%{QUERY_STRING} [L]

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

########## 2015 Redirects ########## 

# Line49 project redirects
Redirect permanent /artwork http://www.domain.ca/_demo
Redirect permanent /demo http://www.domain.ca/_demo
Redirect permanent /login http://domain.ca/manage
#Redirect permanent /help
#Redirect permanent /mockups
Redirect permanent /site-map https://docs.google.com/spreadsheet/ccc?key=0AvzqfV61YfTKdGVtbGtpSzN2OWR6S2hIX2FxdzJHZlE&usp=sharing

# Global Redirects (see also Wildcard redirects above)

#Redirect permanent /vancouverlistings/realestate/featured-listings/itemlist/tag/ http://www.domain.ca/tag/
#Redirect permanent /vancouverlistings/realestate/sold/itemlist/tag/ http://www.domain.ca/tag/
#Redirect permanent /vancouverlistings/component/k2/itemlist/tag/ http://www.domain.ca/tag/
#Redirect permanent /vancouverlistings/itemlist/tag/ http://www.domain.ca/tag/

# CONTENT

Redirect permanent /get-started http://www.domain.ca/contact/get-started
Redirect permanent /vidoe-library http://www.domain.ca/video-library
Redirect permanent /category/vidoe-library http://www.domain.ca/category/video-library
Redirect permanent /faq http://www.domain.ca/knowledge
Redirect permanent /contact-us http://www.domain.ca/contact
Redirect permanent /testimonials http://www.domain.ca/about/testimonials

# Client URL changes
Redirect permanent /the-ivy-on-dunbar-condo-living-on-vancouvers-enviable-westside-pricing-floor-plans-coming-soon http://www.domain.ca/the-ivy-on-dunbar-condo-living-on-vancouvers-enviable-westside

# BLOG

Redirect permanent /blog/2007/ http://www.domain.ca/
Redirect permanent /blog/2008/ http://www.domain.ca/
Redirect permanent /blog/2009/ http://www.domain.ca/
Redirect permanent /blog/2010/ http://www.domain.ca/
Redirect permanent /blog/2011/ http://www.domain.ca/
Redirect permanent /blog/2012/ http://www.domain.ca/
Redirect permanent /blog/2013/ http://www.domain.ca/
Redirect permanent /blog/2014/ http://www.domain.ca/
Redirect permanent /blog/2015/ http://www.domain.ca/

and then there are more redirects after the bad code.

Hope that helps

Thank you for looking into this.

Hi,

Well the .htaccess file got corrupted again. This is the code that is causing a problem this time:

#WFIPBLOCKS - Do not remove this line. Disable Web Caching in Wordfence to remove this data.
Order Deny,Allow
#Do not remove this line. Disable Web Caching in Wordfence to remove this data - WFIPBLOCKS
#WFCACHECODE - Do not remove this line. Disable Web Caching in Wordfence to remove this data.
<IfModule mod_deflate.c>
	AddOutputFilterByType DEFLATE text/css text/x-component application/x-javascript application/javascript text/javascript text/x-js text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon application/json
	<IfModule mod_headers.c>
		Header append Vary User-Agent env=!dont-vary
	</IfModule>
	<IfModule mod_mime.c>
		AddOutputFilter DEFLATE js css htm html xml
	</IfModule>
</IfModule>
<IfModule mod_mime.c>
	AddType text/html .html_gzip
	AddEncoding gzip .html_gzip
	AddType text/xml .xml_gzip
	AddEncoding gzip .xml_gzip
</IfModule>
<IfModule mod_setenvif.c>
	SetEnvIfNoCase Request_URI \.html_gzip$ no-gzip
	SetEnvIfNoCase Request_URI \.xml_gzip$ no-gzip
</IfModule>
<IfModule mod_headers.c>
	Header set Vary "Accept-Encoding, Cookie"
</IfModule>
<IfModule mod_rewrite.c>
	#Prevents garbled chars in cached files if there is no default charset.
	AddDefaultCharset utf-8

	#Cache rules:
	RewriteEngine On
	RewriteBase /
	RewriteCond %{HTTPS} on
	RewriteRule .* - [E=WRDFNC_HTTPS:_https]
	RewriteCond %{HTTP:Accept-Encoding} gzip
	RewriteRule .* - [E=WRDFNC_ENC:_gzip]
	RewriteCond %{REQUEST_METHOD} !=POST
	RewriteCond %{HTTPS} off
	RewriteCond %{QUERY_STRING} ^(?:\d+=\d+)?$
	RewriteCond %{REQUEST_URI} (?:\/|\.html)$ [NC]

	RewriteCond %{HTTP_COOKIE} !(comment_author|wp\-postpass|wf_logout|wordpress_logged_in|wptouch_switch_toggle|wpmp_switcher) [NC]

	RewriteCond %{REQUEST_URI} \/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)(.*)$
	RewriteCond "%{DOCUMENT_ROOT}/wp-content/wfcache/%{HTTP_HOST}_%1/%2~%3~%4~%5~%6_wfcache%{ENV:WRDFNC_HTTPS}.html%{ENV:WRDFNC_ENC}" -f
	RewriteRule \/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)\/*([^\/]*)(.*)$ "/wp-content/wfcache/%{HTTP_HOST}_$1/$2~$3~$4~$5~$6_wfcache%{ENV:WRDFNC_HTTPS}.html%{ENV:WRDFNC_ENC}" [L]
</IfModule>
#Do not remove this line. Disable Web caching in Wordfence to remove this data - WFCACHECODE

So it looks like Wordfence may be the issue. I am not sure what in the above is causing the problem, but when I remove the whole block, the site works again. We weren’t getting a 500 error this time, the site just looked like it was missing all of the css.

So, what other security/caching plugins to you recommend using with your Simple Firewall? We need frequency/brute force banning. Simple Firewall seem to only handle login brute force attempts, but not other kinds of brute force attempts. It also doesn’t seem to automatically ban IP addresses when an IP address has made a number of hacking or bad login attempts. An email is sent, but the IP isn’t blocked.

Thank you.