[wp-meta] [Making WordPress.org] #3090: WordPress.org API not accessible over IPv6 (was: Wordpress.org API not accessible over IPv6)

Making WordPress.org noreply at wordpress.org
Fri Sep 1 11:20:50 UTC 2017


#3090: WordPress.org API not accessible over IPv6
-------------------------+------------------
 Reporter:  deaky        |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:               |
-------------------------+------------------
Description changed by SergeyBiryukov:

Old description:

> We run multiple Wordpress instances on hosts which are '''IPv6 only'''.
> These websites are used internally where we recently transitioned to IPv6
> completely and disabled IPv4 for simplicity.
> Unfortunately your [https://codex.wordpress.org/WordPress.org_API API] at
> ''api.wordpress.org'' does not seem to support IPv6. At least it doesn't
> have any ''AAAA'' records set. Therefore we are not able to use Wordpress
> features like auto updates or plugin installation which connect to your
> API.
> You’d make maintaining our WP instances a lot easier if you added support
> for IPv6 to your API.

New description:

 We run multiple WordPress instances on hosts which are '''IPv6 only'''.
 These websites are used internally where we recently transitioned to IPv6
 completely and disabled IPv4 for simplicity.
 Unfortunately your [https://codex.wordpress.org/WordPress.org_API API] at
 ''api.wordpress.org'' does not seem to support IPv6. At least it doesn't
 have any ''AAAA'' records set. Therefore we are not able to use Wordpress
 features like auto updates or plugin installation which connect to your
 API.
 You’d make maintaining our WP instances a lot easier if you added support
 for IPv6 to your API.

--

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3090#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list