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

[Making WordPress.org]

#3090: WordPress.org API not accessible over IPv6
-------------------------+-------------------------
 Reporter:  deaky        |       Owner:
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:  maybelater
 Keywords:               |
-------------------------+-------------------------

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.

--

Comment (by dd32):

 Replying to [comment:3 Paul Guijt]:
 > OK, I regretfully respect that. But could you please take care that a
 ticket is opened to have WordPress communicate with Wordpress.org and
 Wordpress.com (and any other site that is only IPv4) through IPv4 only?

 This is a server configuration issue on the hosts end. As only IPv4 DNS
 records are returned, it's up to the hosts PHP configuration being
 configured correctly to connect over IPv4. If an IPv4 gateway isn't
 available and only IPv6 is enabled, then it would be expected that the
 HTTP requests would fail quite fast due to the underlying network not
 supporting it.

 WordPress.org's API will be available over IPv6 some day when our hosting
 infrastructure supports it, so we're not going to lock it down to only
 occurring over IPv4.

 There have been some bugs in PHP's CURL implementation in the past which
 causes IPv4 connections to fail on IPv6-only hosts even when a IPv4
 gateway is present which can't be worked around reliably from within
 WordPress.

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