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

There is no way to resolve host in advance and connect to HTTPS server with SNI. #4395

Closed
alexey-milovidov opened this issue Jan 15, 2024 · 3 comments
Assignees

Comments

@alexey-milovidov
Copy link
Contributor

alexey-milovidov commented Jan 15, 2024

This is a continuation of #3456, which was mistakenly closed by the offensive "stale" bot.
This is a continuation of #3123, which was mistakenly closed by the offensive "stale" bot.

It does not matter if four years have passed. The issue is still relevant.

@micheleselea
Copy link
Contributor

I think it's possible just using this

Poco::Net::SocketAddress sa(IP-ADDRESS, PORT);
Poco::Net::SecureStreamSocket ss(sa, "DNS FOR SNI");

@aleks-f
Copy link
Member

aleks-f commented Jan 16, 2024

mistakenly closed by the offensive "stale" bot.

It is not a mistake and the bot is there not to offend anyone, but rather to (1) remind OP what's going on with their issue, and (2) to help us remain sane by keeping the number of opened issues reasonable.

It does not matter if four years have passed. The issue is still relevant.

It does not matter how many years passes - if nobody cares enough to send a fix, the issue will eventually be automatically staled and closed. And I mean a proper fix, not a workaround hack.

Your turn - send the fix and we'll include it in a future release.

@aleks-f aleks-f added this to the Unspecified milestone Jan 16, 2024
@aleks-f
Copy link
Member

aleks-f commented Jan 16, 2024

I think it's possible just using this

Poco::Net::SocketAddress sa(IP-ADDRESS, PORT); Poco::Net::SecureStreamSocket ss(sa, "DNS FOR SNI");

That's not what the issue is about; the problem happens on reconnect

@aleks-f aleks-f added the bug label Jan 16, 2024
@aleks-f aleks-f modified the milestones: Unspecified, Release 1.13.1 Jan 17, 2024
@aleks-f aleks-f modified the milestones: Release 1.13.1, Release 1.14.0 Feb 4, 2024
@aleks-f aleks-f added this to 1.14 Feb 4, 2024
@aleks-f aleks-f moved this to In Progress in 1.14 Oct 30, 2024
aleks-f added a commit that referenced this issue Oct 30, 2024
@aleks-f aleks-f added the fixed label Oct 30, 2024
@aleks-f aleks-f moved this from In Progress to Done in 1.14 Oct 30, 2024
aleks-f added a commit that referenced this issue Nov 5, 2024
@matejk matejk closed this as completed Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

4 participants