-
Notifications
You must be signed in to change notification settings - Fork 40
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
Unix domain socket SOCKS proxy support #47
Comments
I'm trying to run your project based on the README so that I can attempt some rudimentary debugging. I'm on linux mint machine In one terminal:
in another:
I know the flask app is working because I can run it normally with What do I need to do? Also, is it possible you can share your FoxyProxy settings (new FoxyProxy) so I can see how you've configured it? There's an export option. |
You can actually reproduce the issue independently of my project. The link to my project was there as a reference on how to configure a Unix-domain-socket SOCKS proxy. Apparently the issue happens only when not using "proxy by patterns". In the following screenshots, I'm configuring the usage of a proxy which is not running. Configuring a non-existent Configuring a non-existent Configuring a non-existent Configuring a non-existent |
The error you are seeing when running
Fixed with:
|
True..... On Firefox, FoxyProxy checks the selected option:
In this particular case, As we have seen in #49, |
Fixed for v8.3 |
On Firefox, FoxyProxy Classic supports configuring SOCKS proxy over Unix domain sockets. This is done by configuring a host of the form
file:///path/to/socket
. The port is ignored.This does not seems to be working anymore with the new version of FoxyProxy. Using a Unix domain socket SOCKS proxy actually works with
proxy.onRequest
():The text was updated successfully, but these errors were encountered: