it works fine for me
Leave the tab on my website open for a day and then when you revisit my site the following day youāll probably see what I see and no amount of hard refreshing will fix it
ok
but it might take a few days as it seems a bit random
What I cannot figure out is why this html page that loads aes.js is getting injected into everything like my font, my css file and my images
Why is it replacing those files ? why is ifastnet doing this ?
Itās destroying my website
POV:
Cloudflare: Time to pull the cache
*Cloudflare pulls the cache
*No visitor provides Cloudflare with any cookies
iFastNet: Oh this guy doesnāt have any cookies
iFastNet: SERVERS! GIVE HIM THE AES.JS PAGE!
*Servers returns aes.js
Cloudflare: Cool so this is the website
Cloudflare: Iām gonna put it into my cache so I donāt have to go to the servers again
*Website breaks because of Cloudflare caching the wrong pages
Thanks that actually makes sense but sadly I donāt think there is anything I can do to fix this
Iāve been looking at cloudflare settings but Iām no expert
What I was trying to do is find if there is a way to detect the aes.js page and force cloudflare to re-read and cache the correct file
I couldnāt see any way to do this
Possibly somebody more familiar with cloudflare might be able to figure this out ?
I donāt think it is possible to configure caching that deeply on a free account (Canāt speak to an upgraded account, donāt have one).
Maybe ask on CF forums?
Iāve seen people ask about this aes.js page issue on cloudflare forum and the replyās just say its an issue with the hosting provider
Convert everything from PHP to HTML
because as far as I can see there is no need for you to have PHP (dynamic pages)
and when you do that, itās super easy to host everything on Cloudflare.
So you are at peace with HITs and with the problem with resources because you are currently using PHP, as well as with the problem with search engines like AI and other things that will be blocked.
An even faster website because there is no āoriginā, but everything is on CF and you decide what will be allowed and what will not (not someone else).
The thought of moving over to cloudflare pages had flashed across my mind for a microsecond but Iāve been with infinityfree for so long and really didnāt want to leave
I really wish I knew what ifastnet thinks about how their security page is screwing up everyone using cloudflare, are they going to fix it ? do they even care ?
I didnāt want to leave either, but I donāt feel guilty because I left,
because there is a difference in who is to blame.
The real reason is that I was literally chased away by IFN.
I have been forced to make drastic changes to the website 3 times so far.
The IFastNet security does seem wrong
Replacing any file request be it a font, css, image or whatever with a html security page seems crazy to me as it causes mime errors all over the place and destroys sites that use a cdn/caching service
A much better solution would be to inject the security code into your html page the same way that other host inject advert code as this should be non-destructive towards cdn/caching services
But I can see a problem with this as the code injection solution wouldnāt prevent hotlinking of files
I think disabling hotlinking could be performed by .htaccess so together this should form a complete solution
But the /.htaccess could be superseded by the users /htdocs/.htaccess so Iām still not sure
Itās not as easy as I first thought thatās for sure
I think my anger towards IFastNet has melted away and has been replaced by sympathy
This is an interesting problem !
I think Iām going to setup a web server and do some experiments