-
Notifications
You must be signed in to change notification settings - Fork 125
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
Libfetch update #373
base: master
Are you sure you want to change the base?
Libfetch update #373
Conversation
This pull request introduces 2 alerts when merging 490cca2 into 01180f9 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging ada5a80 into 01180f9 - view on LGTM.com new alerts:
|
a717693
to
1dac923
Compare
1dac923
to
2b04789
Compare
…ed encoding works
2b04789
to
e404e83
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had wanted to do this, thanks for getting to it :)
The part where they try to propagate errors from close(fd)
seems weird, but they must have a reason for it.
From what I understood last I looked at FreeBSD libfetch, they implemented their own SOCKS5 handling. Is it compatible with the interface in ours?
Syncing most of the code with the FreeBSD version
and fixing some things about the keep-alive handling.
This should fix some problems and make it easier to resolve #152.
I've been testing this with a bash script: