That’s a 502 error, not a 520 error. A 502 error means that Cloudflare wasn’t able to connect to the origin web server at all, usually because of a problem on the web server’s side, not Cloudflare’s. Again, in this case, it’s the security system’s interaction with Cloudflare.
5 Likes
Due to recent events (I’m asking about aes)
does anyone know what would happen if I chose this on Cloudflare ?
Does this have any side effects related to aes.js or are the two not related and are they run separately?
My brain is not working anymore because I’m already in a rush so I’m pissed off that I have to deal with a million things 3 times a year because someone changes the way hosting works, so I apologize in advance if this is a stupid question.
Note that in 90% of cases I use “cache all in CF”, and for PHP it didn’t matter to me because it doesn’t change
btw. it’s really a lottery to purge cache on CF at the right moment
otherwise aes.js breaks my icons (font pack) and a bunch of other documents and scripts.
JS - what is async has problems… and lazyloading
so slidershow and galleries also have problems for me
like if Cloudflare fails to pull everything into its cache because of aes that interferes with the process and then “holes” remain (pictures or something else missing).
It’s hard for me to figure out where the problem is
because every refresh I feel like I get a different result…
4 Likes
It will treat example.com/pic.jpg?ignore=this-query-string or example.com/pic.jpg?with=query as
this
example.com/pic.jpg
No idea. I believe that websites that depend on query strings will break
3 Likes
I asked it in their support and they said:
Hi there,
This is a permanent change and intended.
Please let us know if there is anything we can do.
5 Likes
Does your website rely on GET parameters to show different pages?
For example, are page.html?view=1 and page.html?view=2 different pages?
If they are, leave it how you have it. If you don’t do this, change it to ignore query string, that should help with caching. It probably won’t help with access though.
5 Likes
I solved everything this way
watch the video until the end for www and the rest.
If someone doesn’t see the difference while visiting my domain, they should do a flush DNS on their PC
In short, CF does everything automatically
I even left the “cache all” rule (I just purged all after I deployed)
6 Likes
Love the way you have resolved this issue! It’s easy to overlook those experimental rules, especially when troubleshooting. Cloudflare’s flexibility is great, but small configurations like that can cause unexpected challenges. Good reminder to review and clean up old rules regularly!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.