Site being accessible via non secure domain.

This is probably caused by an improper order of htaccess rules. If you are using a force SSL or force www/non-www rule in htaccess. Please remove these rules from .htaccess, and insert them in Swift, Settings > General > Tweaks > Custom htaccess.

We are not using any SSL forward in .htaccess.

# Begin cache control #
ExpiresActive on
<FilesMatch "\.(css|bmp|png|ico|gff|js|jpg|jpeg|gif|gcf)$">
FileETag MTime Size
ExpiresDefault "now plus 240 minutes"
</FilesMatch>

ExpiresDefault "now plus 60 minutes"
ExpiresByType text/html "now plus 60 minutes"
<FilesMatch "\.(htm|html)$">
FileETag MTime Size
ExpiresDefault "now plus 60 minutes"
</FilesMatch>

# End cache control #
AddHandler application/x-httpd-php70 .php

# BEGIN WordPress
AddHandler application/x-httpd-php70 .php
<IfModule mod_expires.c>
	ExpiresActive On
	ExpiresByType image/jpg "access plus 6 hours"
	ExpiresByType image/jpeg "access plus 6 hours"
	ExpiresByType image/gif "access plus 6 hours"
	ExpiresByType image/png "access plus 6 hours"
	ExpiresByType text/css "access plus 6 hours"
	ExpiresByType application/pdf "access plus 1 week"
	ExpiresByType text/javascript "access plus 6 hours"
	ExpiresByType text/html "access plus 10 minutes"
	ExpiresByType image/x-icon "access plus 1 year"
	ExpiresDefault "access plus 3 hours"
</IfModule>
<ifModule mod_headers.c>
Header set X-Endurance-Cache-Level "2"
</ifModule>
<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

• This reply was modified 6 years, 2 months ago by suncoastorganics.

We are not using any SSL forward in .htaccess. I posted the code but for some reason it is being held for moderation.

I also noticed that this plugin does not properly enable gzip either. We now have it enabled using htaccess.

I do not understand how others are not having the same issues. We basically only have OceanWP, Woocommerce and Elementor installed.

• This reply was modified 6 years, 2 months ago by suncoastorganics.

I′m affraid you didn′t set Swift properly. At the bottom of the source I noticed this line: <!–Generated by Endurance Page Cache–> How is this related to Swift?

Did I say that it was? I had to disable Swift because it allows the site to be accessed via our insecure domain.

Endurance Page Cache is set up by the the webhost.

And what does that have to with the problems I have mentioned??

How can I have a disabled Plugin not set up properly?

When it was enabled properly it did not properly enable gzip and it allowed the site to be accessed via our insecure domain.

We do not have any optimization plugins installed other than swift and never have.

• This reply was modified 6 years, 2 months ago by suncoastorganics.
• This reply was modified 6 years, 2 months ago by suncoastorganics.
• This reply was modified 6 years, 2 months ago by suncoastorganics.
• This reply was modified 6 years, 2 months ago by suncoastorganics.
• This reply was modified 6 years, 2 months ago by suncoastorganics.

Before using Swift Performance you need to disable endurance-page-cache. This plugin is installed in MU-plugins folder. There you need to rename these 3 files:
php-edge.php to 1php-edge.php
endurance-browser-cache.php to 1endurance-browser-cache.php
endurance-page-cache.php to 1endurance-page-cache.php

Then (re)install Swift and run Autowizard. Please make sure your .htaccess file is writable and remove the rules from # Begin cache control # till </ifModule>.

Hey Fred,

Thanks for the help. We are busy working on the site right now so we do not have to time to deal with this. When we have the time we may attempt to reinstall Swift and see if we can get it working.

Does everyone who installs this need to do that? I am just curious as to why it was not mentioned in the installation instructions.

• This reply was modified 6 years, 2 months ago by suncoastorganics.

Hi,

Thanks for letting us know.

Regarding to your last question, no, this was very specific and related to endurance-page-cache. I’m going to go ahead and mark this topic as resolved. Don’t hesitate to reopen or create a new topic if you still need help!

For now, All the best for 2019.

Fred,

What I am asking is: Why is our site having this issue when other sites don’t?

What is different about our site up that is resulting in problems with this Plugin?

Regards
Mike

Hi Mike,

Swift is currently running on 20k+ sites and most of them without any issue. As there are so many unique server and WordPress environments running, sometimes we need to adjust some extra configuration.

Important is that forced rewrite rules are set before Swift rules in .htaccess, but sometimes a third party (redirect) plugin can also cause some issues.

In your case, it could be related or the other cache layer (endurance) could be responsible for this specific issue in combination with Swift.

Thanks Fred,

I would like to be able to get it fully run down before reinstalling.