Fix regression with HTTPS proxies due to wrong TLS SNI resolution - #91
Merged
Alkarex merged 1 commit intoSep 20, 2026
Merged
Conversation
This was referenced Sep 20, 2026
Alkarex
pushed a commit
to FreshRSS/FreshRSS
that referenced
this pull request
Sep 26, 2026
) Fixes #9314 More details: #9314 (comment) Short version is that I forgot to consider CURLOPT_RESOLVE, since I was focused on making sure that socks4a and socks5h behaved correctly. SimplePie fork PR: FreshRSS/simplepie#91 (there would be problems only with some HTTPS proxies, such as the one described in the issue)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
FreshRSS/FreshRSS#9341