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
Documentation incorrectly states that any software accepting CONNECT method could be used as a proxy #170
Comments
If anyone is interested, I have patched Tinyproxy to implement HTTP ping response required by Scrapoxy, so you can install it by building from source from nirvana-msu/tinyproxy, scrapoxy branch. Coupled with these fixes for #171 and #172, as well as a proper config to set tag on AWS instances, I now have a properly working setup where proxy instances correctly validate Basic Auth. I would say the documentation regarding the gotchas when using 3rd party proxy software still needs to be updated. And it should also be made clear in the doc that built-in proxy instances do not validate authorization header (and are thus open proxies available for anyone to use). P.S. I've also used the (currently cheapest) |
Hi, setuped your branch and compiled tinyproxy - now i started scrapoxy with
(used node 14) but when trying http urls there is this error:
and for https urls:
which node version did you use? |
corrected with 4.0.0 (all traffic is now encrypted with dedicated TLS certificates between master and proxies) |
Hey there! 🌟 Exciting news! Scrapoxy 4 is ready to rock 🚀. Check it out at Scrapoxy.io (explore the "get started" guide, deployment documentation, and more 📚). |
Hello,
I was trying to build by own image with a 3rd party HTTP proxy.
Expected Behavior
According to the documentation:
Actual Behavior
This is not the case because Scrapoxy expects to receive 200 response on http://xx.xx.xx.xx:3128/ping endpoint which no other proxy software implements. Scrapoxy thus considers the instance to be dead if you simply install Tinyproxy / Squid etc.
The problem with built-in NodeJS proxy is that it does not support auth - and I want to avoid hosting an open proxy.
And, despite what the documentation claims, I cannot simply install Tinyproxy because it is unaware that it needs to respond to
/ping
requests. The only solution I can think of (other than extending existing NodeJS proxy with auth) is the put Tinyproxy behind e.g. a reverse proxy which would respond to/ping
request and relay all other requests / responses to Tinyproxy listening internally on a different port. This is obviously far from ideal, and at the very least documentation should be corrected to reflect that.Thanks,
The text was updated successfully, but these errors were encountered: