Community Support Forums — WordPress® ( Users Helping Users ) — 2011-09-16T09:00:43-05:00 http://www.primothemes.com/forums/feed.php?f=5&t=14274 2011-09-16T09:00:43-05:00 http://www.primothemes.com/forums/viewtopic.php?t=14274&p=37312#p37312 <![CDATA[Re: Tip: Salt HTTPS pages]]> on. Under HTTP, the value is actually NULL (the value is unset), but does not seem to be a problem on Apache.

You may need to use a more complex tertiary construct (someone check my syntax):

Code:
((isset($_SERVER['HTTPS']))) ? "on" : "off"


According to the documentation, the syntax error message implies you typed something wrong into the field, rather than the return value being invalid. Hope this helps.

Statistics: Posted by PseudoNyhm — September 16th, 2011, 9:00 am


]]>
2011-09-16T08:39:39-05:00 http://www.primothemes.com/forums/viewtopic.php?t=14274&p=37310#p37310 <![CDATA[Re: Tip: Salt HTTPS pages]]>
Also tried with $_SERVER["SERVER_HOST"] same problem - my theory was that ["HTTPS"] is empty if a page is served via http...

Anyone else got any ideas for how to separate caching of http and https pages?

Statistics: Posted by ksaynor — September 16th, 2011, 8:39 am


]]>
2011-07-28T20:49:15-05:00 http://www.primothemes.com/forums/viewtopic.php?t=14274&p=29430#p29430 <![CDATA[Tip: Salt HTTPS pages]]>
I've found it useful to add the following to the MD5 Salt to separate HTTPS cached content from non-secure content: $_SERVER['HTTPS']

Without this, while browsing HTTPS, Quick Cache would provide a previously cached page, which was generated during an HTTP session. This results in http:// links instead of https:// as they should be if browsing HTTPS. Consequently, users would be exiting and entering HTTPS mode based on the cached version.

To avoid potential security issues related to this, I'd like to recommend that Quick Cache add a built-in feature to differentiate HTTPS from HTTP cached content.

Statistics: Posted by PseudoNyhm — July 28th, 2011, 8:49 pm


]]>