#56042 closed defect (bug) (reported-upstream)
force enable SNI in socks request if SNI supported
Reported by: | puvipavan | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | major | Version: | 6.1 |
Component: | HTTP API | Keywords: | has-patch |
Focuses: | administration | Cc: |
Description
Hello there,
It's 2022 and most of the servers are dropping support for the non sni supported clients.
Following line disables SNI if the verify peer is disabled. It leads to connection error if the server does not support non SNI clients.
Please fix it.
Thanks!
Change History (6)
This ticket was mentioned in PR #2855 on WordPress/wordpress-develop by Puvipavan.
2 years ago
#1
#2
@
2 years ago
Please let me know if I need to do anything for this PR: https://github.com/WordPress/wordpress-develop/pull/2855
#3
@
2 years ago
- Milestone Awaiting Review deleted
- Resolution set to reported-upstream
- Status changed from new to closed
Hello @puvipavan,
Welcome to WordPress Trac! Thank you for opening the ticket.
The change requested is part of the Requests, which is a separate library maintained here https://github.com/wordpress/requests. WordPress Core consumes that library but work on it is within its repo.
I'd suggest opening an issue here https://github.com/WordPress/Requests/issues and then potentially opening a PR here https://github.com/WordPress/Requests/pulls.
I'll go ahead and close this ticket as reported upstream. If you could please (really appreciate you), add a comment to this ticket with the link to the issue you open in Requests. Why? That way the 2 tickets are wired together and anyone reading this ticket will be redirected to follow progress in the Requests repo.
#4
@
2 years ago
Hi @hellofromTonya
No problem. Thanks for your suggestion. Here is the issue link: https://github.com/WordPress/Requests/issues/757
Trac ticket: 56042