Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How exactly do you bypass Cloudflare? #111

Open
MagicalDrizzle opened this issue Aug 30, 2023 · 2 comments
Open

How exactly do you bypass Cloudflare? #111

MagicalDrizzle opened this issue Aug 30, 2023 · 2 comments

Comments

@MagicalDrizzle
Copy link

This particular screen:
cloud
I know it's because of referrers because disabling this extension immediately resolved the issue.
I have tried these rules but it doesn't seem to work...(both Keep and Target)
cl

@airtower-luna
Copy link
Owner

airtower-luna commented Aug 30, 2023

Can you check exactly which request fails? The easiest way to do that is probably the network tab in the developer tools.

The rules shown in your screenshot will (in order):

  • Keep the Referer the same when a sevenforums.com site or frame makes a request to challenges.cloudflare.com
  • Keep the Referer the same when challenges.cloudflare.com site or frame makes a request to sevenforums.com

But without seeing the request that fails I can't say if those are actually the rules you need.

@airtower-luna
Copy link
Owner

One addition: The only website using that Cloudflare "challenge" thing that I use is gitlab.com, so I checked how it loads there. There the gitlab.com page loads an iframe from challenges.cloudflare.com (works fine with Referer removed, which is my default setting for requests to other domains), and that frame then makes a few more requests to challenges.cloudflare.com (so the same domain rule applies). I have set "prune" for same-domain requests, and with that setting it works.

If you have a more restrictive setting for same-domain requests you might want to add a rule for challenges.cloudflare.com to challenges.cloudflare.com requests and set that to "prune" (or "keep").

But it's also possible that forum site uses Cloudflare differently than GitLab, in case of doubt it's best to look at the actual requests and see where there's an odd failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants