[wp-trac] [WordPress Trac] #12609: Enabling FORCE_SSL_ADMIN breaks wp-cron.php
WordPress Trac
noreply at wordpress.org
Sun Apr 9 12:59:19 UTC 2017
#12609: Enabling FORCE_SSL_ADMIN breaks wp-cron.php
--------------------------+--------------------------
Reporter: dphiffer | Owner: johnbillion
Type: defect (bug) | Status: closed
Priority: normal | Milestone: 4.0
Component: HTTP API | Version:
Severity: normal | Resolution: fixed
Keywords: has-patch | Focuses:
--------------------------+--------------------------
Comment (by pavelevap):
Strange, I ran into reverse issue. After switch to HTTPS, cron stopped
working and I had to add following line to enable it again:
`add_filter( 'https_local_ssl_verify', '__return_true' );`
{{{
cURL 7.45.0
OpenSSL/1.0.2g
}}}
Default request ending with `Operation timed out after 0 milliseconds with
0 out of 0 bytes received`, cron did not worked:
{{{
* Trying 2a00:1ed0:1:1800:7:3e:e600:1...
* Connected to www.example.com (2a00:1ed0:1:1800:7:3e:e600:1) port 443
(#0)
* ALPN, offering http/1.1
* Cipher selection:
ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs
* Operation timed out after 0 milliseconds with 0 out of 0 bytes received
* Closing connection 0
}}}
After change it works:
{{{
* Trying 2a00:1ed0:1:1800:7:3e:e600:1...
* Connected to www.example.com (2a00:1ed0:1:1800:7:3e:e600:1) port 443
(#0)
* ALPN, offering http/1.1
* Cipher selection:
ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs
* SSL connection using TLSv1.2 / DHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=example.com
* start date: Jan 23 22:08:00 2017 GMT
* expire date: Apr 23 22:08:00 2017 GMT
* subjectAltName: www.example.com matched
* issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
* SSL certificate verify ok.
> GET /wp-cron.php?doing_wp_cron=1491666257.9983050823211669921875
HTTP/1.1 Host: example.com Accept: */* < HTTP/1.1 200 OK
< Date: Sat, 08 Apr 2017 15:44:22 GMT
< Server: Apache < X-Powered-By: PHP/5.6.20-pl0-gentoo
< Expires: Wed, 11 Jan 1984 05:00:00 GMT
< Cache-Control: no-cache, must-revalidate, max-age=0
< Pragma: no-cache
< Content-Length: 0
< Content-Type: text/html; charset=UTF-8
< * Connection #0 to host www.example.com left intact
}}}
I am not sure if something is wrong with server settings or it is any
WordPress bug. Any idea?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/12609#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list