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.

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

Add --cacert and --proxy-cacert #109

Merged
merged 3 commits into from
Nov 2, 2022
Merged

Add --cacert and --proxy-cacert #109

merged 3 commits into from
Nov 2, 2022

Conversation

nwf-msr
Copy link
Contributor

@nwf-msr nwf-msr commented Nov 1, 2022

See #108 While here, fix two other nits.

`FREE()` checks for a `NULL` pointer, but generally httpdirfs does not
`NULL` out pointers it attempts to `FREE()` (or `free()`).  As such, the
error message is misleading; make it less so in a trivial way.

Possibly a better, more invasive, change would be for `FREE()` to take a
`void** pp`, check that `*p != NULL`, `free(*p)`, and then `*p = NULL;`.
Were that done, then there would be some plausibility to the current
diagnostic message.
It's entirely possible that `ts.data` is `NULL` on an error path, so
handing it to `FREE()`, which bails on a `NULL` argument, is not ideal.
Just pass it to `free()` instead, which is required to no-op if given
`NULL`.
@fangfufu fangfufu merged commit bb3b652 into fangfufu:master Nov 2, 2022
@fangfufu
Copy link
Owner

fangfufu commented Nov 2, 2022

Looks good to me, thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants