2 blazor-university.com/*
SSL: Full, Auto Minify: HTML, CSS & JS, Rocket Loader: On, Browser Cache TTL: a day, Always Online: On, Cache Level: Cache Everything, Edge Cache TTL: a month, IP Geolocation Header: On
My server often returns 503 errors because it is overloaded, I noticed that the AWStats say in May I’ve had 18,336 visitors and served 103,623 pages.
I wouldn’t expect anything like this number of hits on my server. What am I doing wrong?
2 blazor-university.com/*
SSL: Full, Auto Minify: HTML, CSS & JS, Rocket Loader: On, Browser Cache TTL: a day, Always Online: On, Cache Level: Cache Everything, Edge Cache TTL: a month, IP Geolocation Header: On
ICO files should be automatically cased, as well as JS files. If they dont it is either caching headers sent by your server which prevent caching or page rules.
Considering your page rules do not seem to prevent it, it probably is the caching headers. Check whatever your server sends, and also use the search here, as that topic has been covered a few times already.
It is a bit unrelated, but in that case the first concern would be that you dont have a valid certificate on your server and hence cant use the only secure encryption mode “Full strict”. That is something you should address.
You do have a certificate but it is self-signed and hence not secure. You should replace that with a proper certificate (can also be an Origin certificate which you download from Cloudflare).
It shouldnt be the main reason for the issue however. Your ICO file, for example, is only a redirect to a PNG file and that file actually gets cached.
That file actually gives me a HIT, however I’d really prefer if you could install a proper certificate as I am not overly comfortable supporting an insecure setup to be honest.
Issueing an Origin certificate takes a few minutes and configuring it on the server shouldnt take much more.
I didn’t think my host made that a simple process, but I found the instructions and have followed them. The origin site should be SSL now, and my SSL option is set to FULL.
I think all of my responses are coming back as HIT now. Is that what you are seeing too? If so, was not having a certificate on my host the cause of the problems?
The certificate shouldnt have been the issue, however the certificate you installed only covers your naked domain. You must have removed the wildcard. Revoke that certificate and get a new one issued with blazor-university.com and *.blazor-university.com. That will also cover “www”.
Looks secure now. And I do get hits too, though that still should not be HTTPS related, but having a proper certificate in place is still important, otherwise the site is not really secure.