• Sign up or login, and you'll have full access to opportunities of forum.

Traffic optimization

Go to CruxDreams.com
I've just checked, I type in www.cruxforums.com and that still accesses the site and lets me log in. The url still shows 'Not secure' and 'cruxforums.com'', no https/ etc. Should I expect that to change?

Indeed, externally hosted images do save cost, and we're grateful that members have been using them for that reason.
But there are a few concerns:
  • the fact that they show up full-size means they're visible to anyone who happens to find the site, whether registered or not
  • successive posts containing full-size images (even several such images) clutter up threads and are not convenient for viewing on many types of equipment
  • some external images carry (hidden) links to source sites, and we're uneasy about the range of unknown and possibly very dodgy sites that are being linked on ours
So we ask members who are posting external hosted images to state where they're hosted.

E--
Thanks for the clarification!
 
When I access using the https method, I no longer get the site insecure message, rather a more middling message that warns some images may be insecure.
curiouser and curiouser, we'll wait to see what happens.

It does alert us to the concern I hinted at above - we want our site to be secure in all senses (even though it's not one where financial details or other confidential information are ever asked for) - and we want sites linked in any ways to ours to be safe and secure ones too - we're alert to the dangers both of malware etc. getting into members' equipment, and of members stumbling into illegal content (kiddie porn etc.) unawares, which is why we're being cautious.
 
When I access using the https method, of no longer get the site insecure message, rather a more middling message that warns some images may be insecure.
For me that happens only on the start page, and not on any of the content pages, that is -- actual threads.
The reason is that a few images on the start page are hard coded as HTTP:// links on the start page - the Help the forum and the donation thermometer images, as fallenmystic has pointed out.

Those are only nitpicks and the rest of the forum is now fully SSL encrypted!

I also see that everything has been switched over new IP's responding for HTTP requests to 'cruxforums.com' (they are v6 now also) and an nslookup call also delivers very different results than it did before. So the CDN switchover really does seem to be working.
 
It does alert us to the concern I hinted at above - we want our site to be secure in all senses
In terms of SSL the security of the site has just increased by leaps and bounds.
The warning on the start page is a rather trivial matter -- with SSL being used it is now no longer possible to 'sniff' login names and passwords during a sign in which was previously technically possible.
 
For me that happens only on the start page, and not on any of the content pages, that is -- actual threads.
The reason is that a few images on the start page are hard coded as HTTP:// links on the start page - the Help the forum and the donation thermometer images, as fallenmystic has pointed out.

Those are only nitpicks and the rest of the forum is now fully SSL encrypted!

I also see that everything has been switched over new IP's responding for HTTP requests to 'cruxforums.com' (they are v6 now also) and an nslookup call also delivers very different results than it did before. So the CDN switchover really does seem to be working.
All this up-to-date technology makes me feel I ought to write better stories:doh:

FWIW, it still says "Not Secure" regardless of where I am on the site.
 
I am now getting a site secure (lock) symbol, plus a notation that says "verified by cloudflare, Inc.". I still get the "some parts of this page are not secure (such as images)" message if I click on the lock symbol.
 
FWIW, it still says "Not Secure" regardless of where I am on the site.
If you still have http://www.cruxforums.com in the adress bar of your browser (you may have to click into it to se the protocol - that is the part before the :// ... and in some browsers that may not be shown at all, with the URL just starting with www.) -- then yes, that will be so.
Anything http:// is insecure.
As of now https:// is available but not enforced upon the user. Previously it was not available.
So right now you can if you want to switch to the https:// version by just either editing the http:// into https://, or adding the https:// in front, if it starts right with www. -- and then hitting Enter on your keyboard. The page will reload and you should get a different security evaluation.
 
If you still have http://www.cruxforums.com in the adress bar of your browser (you may have to click into it to se the protocol - that is the part before the :// ... and in some browsers that may not be shown at all, with the URL just starting with www.) -- then yes, that will be so.
Anything http:// is insecure.
As of now https:// is available but not enforced upon the user. Previously it was not available.
So right now you can if you want to switch to the https:// version by just either editing the http:// into https://, or adding the https:// in front, if it starts right with www. -- and then hitting Enter on your keyboard. The page will reload and you should get a different security evaluation.
I did that and it still says Not secure
 
The insecure warning about images is caused by the problem I mentioned in my previous post. In short, if a site is to be strictly secure, all of its contents must be served via HTTPS.

But the problem is, we have 2 images (the thermometer and "HELP US..." banner) which are still referenced by the old HTTP address. It's most likely because their full URLs are manually entered somewhere so we can just find and change them, as I detailed in my previous post.

The important thing to note is "all of its contents" does not include images hosted on an external service. As such, using HTTP URL to images hosted on an external site does not cause such a problem.

As to the reason why some of you still get redirected to HTTP is also explained in my previous post along with a solution. It's really an easy fix, but there may be a little complication as I suspect there may be a XenForo setting where the old URL (beginning with "http://") is entered manually, which may cause an endless loop if the Cloudflare option is toggled on. That was why I warned about the possiblity in "EDIT".

In short, you need to type "https://www.cruxforums.com/xf/" (with the trailing "/") to enter the secure site at the moment, because otherwise, there's something (likely to be some hardcoded setting on the XenForo's admin console) redirects you back to the old site. It's just a matter of changing the address on the console, but finding where the setting is might be a bit tricky.

All these problems are relatively easy to fix and something we won't have to worry about once we get past them (unlike the problem with the traffic). So we can regard them as temporary inconveniences of transitioning to a more secure website.

Hope this helps to clear up some of the confusion.
 
Last edited:
In short, you need to type "https://www.cruxforums.com/xf/" (with the trailing "/") to enter the secure site at the moment,

Hope this helps to clear up some of the confusion.

I tried that, and it didn't work at first. I found out that I needed to completely log out of cruxforums first and then exit the site. Then, when I entered https://www.cruxforums.com/xf/, I got directed to the secure site. I could then log in as usual.

I now feel so secure, I'm thinking of flushing all my Prozac!

:juggle: :jump1: :applaudit:
 
I think FM and Poem have made this clear, but just to reinforce the message:

Log in as: https://www.cruxforums.com/xf/

and the insecure site issue goes away.

Note. one may have to log out first, though, if one has the setting “stay logged in” on one’s account in order to clear any account memory of the old insecure log in.
 
Last edited:
I think FM and Poem have made this clear, but just to reinforce the message:

Log in as: https://www.cruxforums.com/xf/

and the insecure site issue goes away.

Note. one may have to log out first, though, if one has the setting “stay logged in” on one’s account in order to clear any account memory of the old insecure log in.
You are right. If you use some browsers like Chrome, however, it will still report the site as insecure as long as the URLs of those two images mentioned above remaine as they are. It's trivial to change them so hopefully it won't take too long before it can be fixed.
 
Back
Top Bottom