Hello again, I hosted some dynamic information on my website and parsing it using my Java application. Later I’ve been bypassing InfinityFree aes.js scripting by Clooudflare. But now I can’t do this, because it still returning script page. So my question is ‘how to bypass infinityfree aes.js right now?’. HELP PLEASE
My last topic with the same problem is → Aes.js is bad - #3 by Admin
This loophole has been patched,
You cannot bypass aes.js anymore
Read below thread for more info
as others have said, you cant. But what you can do (maybe) is adjust your javascript or php to ignore the i=1. i’ve done it a couple of times now, so if you need a hand I’ll see what I can do
That would be nice, but I have to take into account the fact that my application sends http requests to the site to read the information output by php. So it would be great if you could help me do something with ?i=1
@dan3008 The AES.JS page/script is being returned instead of the intended script.
May not work out for this person.
Unfortunately, this AES.JS loophole has been patched, and there isn’t a solution to this.
Please Note that InfinityFree is a Web Hosting provider, intended to be used to display websites. Please Take A Peek:
Hell noooo
Apologies for the inconvenience, but it is something that isn’t in our control. If you need this functionality, you can try Premium Hosting.
ah I see. Unfortunaitly thats not something you can do on infitiy free, as @Jri-Creator said.
The rules for our hosting are the same regardless of whether you use Cloudflare or not: it’s website hosting, i.e. hosting intended to host web pages viewed in browsers.
It used to be that websites using Cloudflare were exempt from the bot protection system, both because the script tended to cause issues with Cloudflare and because we assumed that Cloudflare provided adequate protection.
However, that doesn’t really seem to be the case and too many attacks are are punching right through Cloudflare. So we managed to fix the script to work with Cloudflare, meaning the rules are the same for everyone again.
I completely understand that this breaks your use case, but please understand that we never supported such API hosting to begin with, or made any guarantees that it would keep working.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.