-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
2 out of 3 proxies are broken #21
Comments
Fixed, thanks.
Yeah, it's broken for some reason. I'll take a look. |
I suspect that the issue is whatever UA is being used, since plain curl grabs the list with no issues. |
Nope, curl doesn't grab either. It seems that CORS proxy adds '=' in the end if the query by mistake. Some sites work, but most don't.
Note |
I've checked - seems that https://api.codetabs.com/v1/proxy/?quest= works for this particular case. I've build your scanner manually, and it seems to work fine and grabs the list succesfully. Tbh, I've know idea whether they have any rate limit or not, but I guess it'll be fine, since this is only one of the options, and the client is not the app per se, but the user's machine in itself. https://universal-cors-proxy.glitch.me works as well, but only if symbols are encoded (i.e. %2F instead of slash, %2C instead of comma and so on). This might be the issue with the app on Vercel, btw. |
Hi there, this is just an FYI.
There are three proxies used for downloading the relay's list: one on Github, one on Bitbucket, and one via another app.
Right now only Github mirror is working (although it lags behind a bit behind onionoo.torproject.org), whilst Bitbucket one is severely outdated (last updated in April), and the other one is outright broken (script can't parse the output).
The text was updated successfully, but these errors were encountered: