Jump to content


Photo
- - - - -

Ssl Switching


  • Please log in to reply
3 replies to this topic

#1 the_hive

the_hive

    Newbie

  • Members

  • 2 posts
  • Country: Country Flag

Posted 08 December 2012 - 11:32 AM

Hi,

I am having an issue with the following page displaying insecure content:

Please Login or Register to see this Hidden Content

 

The CSS was completely broken and below is the assessment from WPengine.

 

"That page is now excluded from our CDN. The assets are *not* loading from our CDN, and they page is still not displaying appropriately.

The problem is that your theme is not taking the protocol into account, and it is not changing http to https when it should, and as other themes do without a problem."

 
I have since changed the header and footer images to https: in Site Options, but they now display that way in the entire site.  From my understanding, the theme should be switching on its own for forced ssl pages.  Any ideas?
Thanks,
Joel


#2 Simon_P

Simon_P

    Messer

  • Administrators



  • 8388607 posts
  • LocationDevon
  • Framework Version:2.1.1
  • Country: Country Flag

Posted 08 December 2012 - 02:20 PM

What do you mean by 'forced ssl'? The framework uses whatever protocol WordPress is using, so if your site_url is https the so is the frameworks. If you using some kind of plugin to trick WordPress into being SSL for one page then your going to have to do the same for the framework.

So how are you doing it?



#3 the_hive

the_hive

    Newbie

  • Members

  • 2 posts
  • Country: Country Flag

Posted 08 December 2012 - 02:34 PM

Thanks for the quick reply Simon.  I'm using an Apache rewrite rule to direct traffic from

Please Login or Register to see this Hidden Content

to

Please Login or Register to see this Hidden Content

 Before I switched the site over to Pagelines, this was not an issue.  Is Pagelines not able to handle this?

Thanks,

Joel



#4 Simon_P

Simon_P

    Messer

  • Administrators



  • 8388607 posts
  • LocationDevon
  • Framework Version:2.1.1
  • Country: Country Flag

Posted 08 December 2012 - 02:42 PM

well yea of course it is, but the CSS is only written once and cached, so if its cached on a non-ssl page the css is going to be non-ssl on the ssl page, if you follow.

 

So your choices are:

 

  • Force the CSS to never cache and re-generate on ever pageload (!)
  • Force the CSS to be SSL on all pages, including non-ssl pages.

 

Please Login or Register to see this Hidden Content

Use the above to force the css to be ssl