Jump to content

Recommended Posts

  • 3 months later...
Posted

Thanks, Ryan for the https config setting.

Few Qs if you've got time

  • Does this need to be manually included in a config? I just updated to  3.0.110 © 2018 and noticed it's not there (possibly is not meant to be).
  • Even after including this, I notice the HTTPS setting in the htaccess file over-rides this. it's be great to have a config that over-rides both the HTTPS and www V non www settings too

 

Posted
5 hours ago, Peter Knight said:

Even after including this, I notice the HTTPS setting in the htaccess file over-rides this

A php setting can never override what htaccess does. PHP is not even started when the htaccess file is read/executed.

  • Like 1
Posted
10 minutes ago, LostKobrakai said:

A php setting can never override what htaccess does. PHP is not even started when the htaccess file is read/executed.

So the config setting ($config->noHTTPS = true; ) is ineffective if there’s a htacess setting of always use https ? 

That seems a bit odd as any site running Http would probably have this htaccess directive enabled for SEO reasons. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...