-
-
Notifications
You must be signed in to change notification settings - Fork 82
Net::HTTP.SOCKSProxy auth support, take 2 #33
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
Conversation
|
Hi, I'd like to see this in a socksify release so I can use it in Faraday. I don't personally use a SOCKS proxy, but I have successfully tested it in my integration suite with Faraday and a golang socks server. Is there any way I can help get this out? /cc Integration test suite PR: technoweenie/faraday-live#7 |
|
is this good to go? |
|
Same question as @guivinicius : what is preventing this PR from being merged for so long ? |
|
Is there anything we can do to move this forward? |
|
Is that dead? |
|
Who wants to become maintainer? |
|
@astro if you are still looking for a maintainer for socksify I'm happy to give it a go. |
|
@MatzFan Thanks. Please be kind to my baby. ;-) |
|
With 40M downloads from rubygems.org I could hardly do otherwise :-) |
|
Oh, I was not aware. In that case I would like to read all changes before publishing to rubygems.org. Please ping me whenever you tag a release. |
|
@astro sure, will do. |
|
Can this be merged? Works well. |
|
Looks like a solid solution. Do you have any blockers to release this? |
dae6100 to
2fd0fc3
Compare
2fd0fc3 to
4af5542
Compare
|
I eventually rebased this one but the linter isn't happy and there are no tests for the new functionality. Before I merge I'd love to get some review and suggestions by you who are more versed with contemporary Ruby practices. |
|
The lack of a test facility for socks authentication was my only objection to adding this functionality, but someone further down that thread said it can be done with SSH. I'll take a look, this is long overdue. |
This MR is inspired by #24, but does not use thread-local variables to store username/password. This is IMO safest and cleanest way to do it.