Skip to content
This repository has been archived by the owner on Mar 5, 2021. It is now read-only.

checks if the proxy bypass a website protected by CloudFlare #1

Open
ghost opened this issue Jun 10, 2020 · 1 comment
Open

checks if the proxy bypass a website protected by CloudFlare #1

ghost opened this issue Jun 10, 2020 · 1 comment

Comments

@ghost
Copy link

ghost commented Jun 10, 2020

Hi,

Hope you are all well !

Is it possible to add an option to proxi for checking if a proxy bypass a website protected by CloudFlare ?

For doing so, we need to find a cloudflare website (list from https://www.wappalyzer.com/technologies/cdn/cloudflare) and http://getbootstrap.com/ sounds like a good choice ?!

And, from my understanding we can add it to the PROXI_JUDGES env variables but can we add it in the database as a specific field/property in the database ?

Cheers,
X

@nicksherron
Copy link
Owner

nicksherron commented Jun 22, 2020

Hey @x0rzkov ,

First off, thanks for your feedback and interest in the project and I apologize for my slow response.

My mother has become terminally ill and its been a struggle trying to juggle paid projects let alone anything open-source, so my attention I can give to this is unfortunately limited at the moment. However, I do plan on continuing development once things get settled and will try to keep up with any issues and pull requests in the meantime.

And finally to answer your question!

This is actually a really good idea and something I have thought about as well. This currently wouldn't be possible because the proxy check process is hardcoded to expect the response from a PROXI_JUDGES request to be a httpbin api like json response, and needs to be rewritten/designed (really the whole project needs this). You can checkout the code for it at internal/check.go#L279 .

The original plan was to let allow any url (or multiple different urls) to be used for checks. What do you about having the option of supplying a list of urls with labels as a config file that the checks run on store the results under each corresponding label? That way if you were gathering proxies for scraping a specific site, for example, you could test them out beforehand.

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

No branches or pull requests

1 participant