Infinityfree webhosting and cloudflare cache issues with aes.js

General
1

What is the name of the domain?

https://lovebyte.eu.org

What is the issue you’re encountering

infinityfree has a html security page that tests for a security cookies and runs an aes.js function, this is so that only browsers can access their hosted websites.
The issue is that infinityfree injects this page on any request for any file not just html and cloudflare caches this page instead of the actual web page or file that follows the security check

What steps have you taken to resolve the issue?

I have looked through the cloudflare caching settings to see if there might be a way to detect this annoying security injection and if found re-cache the actual file but I have been unable to do this

What are the steps to reproduce the issue?

The infinityfree security is in place so that only web browsers can access the site files
The way it functions is that when a request (any request for any file !) is made the sever injects a html file with an aes.js script and this thing checks a cookie has been set
So only something able to run javascript and set cookies is allowed to access the site (a browser)

The issue is that infinityfree injects this page before the real file and doesn’t care what its replacing, it could be an image or a css file or anything which causes a mime error
But worst of all is that cloudflare then caches this idiotic security html file as the actual original requested image or css or whatever and then the site is totally broken

I know this isn’t a cloudflare issue but an infinityfree issue but their parent company ifastnet who provide the hosting doesn’t seem to want to fix this broken mess so I was wondering if there is any way that I can set up a rule to automatically detect if this stupid security page got cached and if so then re-read the file to then cache the correct file ?

Thanks

2

sorry I forgot screen shots

this is how it looks when the correct files are cached

image
image1366×768 146 KB

this is how it looked when the security page was injected instead of my css file

image
image1121×650 73.4 KB

At other times it might be my nasa.otf font file that gets clobbered or some other file so things vary each time

The issue is that I think the security page has to run 3 times to update the cookie before the servers stop injecting the file and as they inject it on any request it will be replacing any file

If I could some how detect if this is cached and then re-cache then I could solve this problem but I so far have been unable to figure out if this is possible with the cache rules

3

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.