HTTPS

[CarpCharacin]

There is a valid SSL certificate set up on this site. You just need to 301 redirect all traffic through HTTPS and enable the image and link proxy to eliminate mixed content warnings. The same goes for theeasygarden.com and sufficientself.com

 

[Nifty]

Thanks, we're definitely looking into it and working on it!

 

[Nifty]

Ok, I think I've got https all fixed on here!

I'm not yet "forcing" everything to be SSL right now, but you can get there direct: https://www.backyardherds.com/

That should add the little "Lock" to the top of the URL.

I'm curious though... does going to that link require you to login again?

 

[CarpCharacin]

No, it dosen't force you to log back in so you can force HTTPS without making people log back in. It is looking like the SSL is issued to backyardcows.com, not backyardherds.com so eneble autossl for this domain if you haven't.

 

[Nifty]

Ok, all of BYH is now under a secure connection!!!

 

[BlessedWithGoats]

Thanks @Nifty for all that you admins/moderators do!

 

[Bruce]

Yes and thanks to @CarpCharacin for the directions.

Oh, and apparently I should be saying to him as well! Hadn't noticed this thread is the first he posted on (and started!) last Friday. I hope you plan to stick around and join the herd

 

[CarpCharacin]

Ok, all of BYH is now under a secure connection!!!

There is still a mixed content warning. It looks like the only no secure origin is nifty-stuff.net.

EDIT: Now it is showing up as secure.

 

[Nifty]

Thanks! It's the images we use for notices. We'll fix that ASAP!

 

[greybeard]

I'm getting the following security notice from my Kapersky Secure URL app when visiting BYH, and only at BYH. Part of the ads or cookies protocol here or simply part of W10's ad campaign?