mirror of
https://github.com/gosticks/wordpress-develop.git
synced 2026-04-04 12:44:31 +00:00
Security, Site Health: Do not store HTTPS request error messages in an option.
This changes the logic in `update_https_detection_errors()` to never store error messages from the actual request since they could use a different encoding, which would make storing them in an option potentially fail, leading WordPress to then falsely assume that HTTPS is supported. While this doesn't actually fix the encoding issue, it is not crucial to do so anyway, since these messages are not used anywhere. A simple differentiation between whether the overall HTTPS request or only the SSL verification failed should be sufficient for the purpose of this function. Props flixos90, tmatsuur, lukecarbis. Fixes #52484. git-svn-id: https://develop.svn.wordpress.org/trunk@50471 602fd350-edb4-49c9-b593-d223f7449a82
This commit is contained in:
@@ -130,13 +130,13 @@ function wp_update_https_detection_errors() {
|
||||
|
||||
if ( is_wp_error( $unverified_response ) ) {
|
||||
$support_errors->add(
|
||||
$unverified_response->get_error_code(),
|
||||
$unverified_response->get_error_message()
|
||||
'https_request_failed',
|
||||
__( 'HTTPS request failed.' )
|
||||
);
|
||||
} else {
|
||||
$support_errors->add(
|
||||
'ssl_verification_failed',
|
||||
$response->get_error_message()
|
||||
__( 'SSL verification failed.' )
|
||||
);
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user