Hack Forums
[News] HTTPS Support Added - Printable Version

+- Hack Forums (https://hackforums.net)
+-- Forum: Hack Forums Official Information (https://hackforums.net/forumdisplay.php?fid=1)
+--- Forum: Site News (https://hackforums.net/forumdisplay.php?fid=2)
+--- Thread: [News] HTTPS Support Added (/showthread.php?tid=5424059)

Pages: Pages 1 2 3 4 5 6 7


* - minimalist - Oct 4, 2016

Congrats on the implementation, unfortunately there'll be other useless unadded features that we'll complain about.


* - Malicious007 - Oct 4, 2016

(Oct 4, 2016 10:12 AM)Rubixa Wrote:  Yeah they are for me

edit: anyone else taking a few seconds to load pages?

everything is taking an extra second


* - Pharmacist - Oct 4, 2016

Loading is actually faster for myself.


* - deject - Oct 4, 2016

https://i.imgur.com/KOLV1kA.png

Issue here...


* - Rubixa - Oct 4, 2016

(Oct 4, 2016 10:15 AM)Craxzy Wrote:  Not a few seconds, its increased but nothing that will be a problem. Not for me at least.

A few seconds on my end, not a problem for me though, was just wondering if anyone else noticed a change.

(Oct 4, 2016 10:16 AM)malicious007 Wrote:  everything is taking an extra second

Yeah so it seems, ah well.


* - ⁠Cammy - Oct 4, 2016

(Oct 4, 2016 10:10 AM)Omniscient Wrote:  I already feel like pages are taking an extra second to load.

If anything it's faster for me
Probably just placebo though


* - Neeeeeeeeeel.- - Oct 4, 2016

What a surprise, you finally get tired of people asking for HTTPS, even when you know it's "useless" for a forum. Now everybody can feel the power of HTTPS!!!!!!!


* - Rubixa - Oct 4, 2016

(Oct 4, 2016 10:17 AM)deject Wrote:  https://i.imgur.com/KOLV1kA.png

Issue here...

Same for me if I go to User CP, a new page/thread etc. but the main site / going into a forum is fine, just opening of threads it becomes broken.


* - ⁠Cammy - Oct 4, 2016

(Oct 4, 2016 10:22 AM)Rubixa Wrote:  Same for me if I go to User CP, a new page/thread etc. but the main site / going into a forum is fine, just opening of threads it becomes broken.

I'm willing to bet it has to do with user signatures and avatars.


* - DopplerAF - Oct 4, 2016

Congratulations to all although it was not needed.

But anyways site looks more legit and sexy.


* - Rubixa - Oct 4, 2016

(Oct 4, 2016 10:23 AM)Cammỵ Wrote:  I'm willing to bet it has to do with user signatures and avatars.

Yeah definitely, just parts of the page not being secure including images.


* - Neeeeeeeeeel.- - Oct 4, 2016

(Oct 4, 2016 10:17 AM)deject Wrote:  https://i.imgur.com/KOLV1kA.png

Issue here...

(Oct 4, 2016 10:22 AM)Rubixa Wrote:  Same for me if I go to User CP, a new page/thread etc. but the main site / going into a forum is fine, just opening of threads it becomes broken.

That's because of non-https user signatures or images posted on thread. It will always happen. While the main page runs HTTPS, the linked third-party resources are not HTTPS so the browsers says: mixed-content, not all the page is "secure".


* - iUpgrade - Oct 4, 2016

Doesn't makes a difference for me, anyway still thanks for your efforts.
Yeah everything works good


* - Rubixa - Oct 4, 2016

(Oct 4, 2016 10:26 AM)Neeeeeeeeeel.- Wrote:  That's because of non-https user signatures or images posted on thread. It will always happen.

Ah.. so if imgur was SSL and everyone on one page of a thread used imgur for images, it'd be fine? I get ya.. Thanks for clearing that up.

Edit:

So if I were to use i.imgur.com/xITDbw2.gif as my signature at the moment, if I were using https://i.imgur.com/xITDbw2.gif I wouldn't be getting the broken SSL at usercp?


* - Neeeeeeeeeel.- - Oct 4, 2016

(Oct 4, 2016 10:28 AM)Rubixa Wrote:  Ah.. so if imgur was SSL and everyone on one page of a thread used imgur for images, it'd be fine? I get ya.. Thanks for clearing that up.

Edit:

So if I were to use i.imgur.com/xITDbw2.gif as my signature at the moment, if I were using https://i.imgur.com/xITDbw2.gif I wouldn't be getting the broken SSL at usercp?
If all the users changes their signatures/avatars/post images to HTTPS, then you will see the green padlock.

If just one referenced resource is called though HTTP protocol, you will see the "mixed-content"/broken SSL padlock.

Also, if someone changed their browser settings to do not allow mixed-content he will get a security warning (just like the one displayed when the certificated is expired). Some years ago this setting was default in most browsers.