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.

Sign up for GitHub

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

Jump to bottom

Defining proxy (SOCKS/HTTP) #5

Open
tasooshi opened this issue Jun 27, 2022 · 2 comments
Open

Defining proxy (SOCKS/HTTP) #5

tasooshi opened this issue Jun 27, 2022 · 2 comments
Labels
enhancement New feature or request
Milestone
v1.2.0

Comments

@tasooshi
Copy link
Contributor

It should be possible to provide arguments for SOCKS or HTTP proxy, must be reflected both in the API and the CLI.

To consider: using both in parallel, for any protocol that has preferences on which one to use?
@tasooshi tasooshi added this to the v1.0 milestone Jun 27, 2022
@tasooshi
Copy link
Contributor Author

tasooshi commented Jul 1, 2022

Moving to the future, requires multiple protocols (services) to be implemented.

@tasooshi tasooshi modified the milestones: v1.0, v1.2 Jul 1, 2022
@tasooshi tasooshi added the enhancement New feature or request label Jul 1, 2022
@tasooshi tasooshi modified the milestones: v1.2, v1.3 Jul 7, 2022
@tasooshi
Copy link
Contributor Author

Considering my recent experiments with socks and proxying, this would be extremely difficult to implement since there's no currently maintained (and working) socks library except for some fresh stuff for asyncio. Instead, user should be instructed how to use other tools for proxying. TBC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
v1.2.0
Development

No branches or pull requests
1 participant
@tasooshi