[wp-trac] [WordPress Trac] #42007: rpc.pingomatic.com still using HTTP

WordPress Trac noreply at wordpress.org
Sat Jul 30 23:25:04 UTC 2022


#42007: rpc.pingomatic.com still using HTTP
------------------------------+------------------------------
 Reporter:  bhubbard          |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Pings/Trackbacks  |     Version:  4.9
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:  administration
------------------------------+------------------------------

Old description:

> It looks like rpc.pingomatic.com still doesn't support https. I would
> like to see it support HTTPS, and then have WordPress default to using
> https for it.
>
> [[Image(https://cl.ly/3Y1H1C2H040v)]]

New description:

 It looks like rpc.pingomatic.com still doesn't support https. I would like
 to see it support HTTPS, and then have WordPress default to using https
 for it.

 [https://cl.ly/3Y1H1C2H040v screenshot of Update Services field]

--

Comment (by sabernhardt):

 Thanks for the report and sorry for the long delay!

 The rpc.pingomatic.com subdomain still does not seem to support HTTPS, but
 I made a patch to update the schema for new sites if the subdomain gets
 SSL.

 All unit tests passed with only the schema.php change. I also wanted to
 update the unit test to check both HTTP and HTTPS, and (only) the
 7.0-multisite test failed. The failure notice mentions a timeout. (I had
 planned to try a pull request on my fork first. :facepalm:)

 When this is completed, the [https://wordpress.org/support/article/update-
 services/ Update Services support article] will need updating (both the
 screenshot and the list).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/42007#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list