SSL access through a proxy causes SIGSEGV #1533
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've found that GET requests via proxy cause SIGSEGV for SSL access.
@yhirose Could you review the following and the PR?
How to reproduce
OS: Ubuntu 22.04.2 (x86_64)
Set up Squid.
Code to reproduce.
Detail
It seems that the problem is originated in the commit c7e959a at the
ClientImpl::process_request
function. I don't understand the implementation details around that code, but it is probably due to the lack of a socket open check, and this seems to fix SIGSEGV.