[wp-trac] [WordPress Trac] #15936: IPv6 literal support in multisite broken
WordPress Trac
noreply at wordpress.org
Tue Apr 21 17:50:56 UTC 2020
#15936: IPv6 literal support in multisite broken
-------------------------------------------------+-------------------------
Reporter: jmdh | Owner: (none)
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Networks and Sites | Version: 3.0
Severity: major | Resolution: maybelater
Keywords: has-patch has-unit-tests dev- | Focuses: multisite
feedback |
-------------------------------------------------+-------------------------
Changes (by jeremyfelt):
* status: assigned => closed
* resolution: => maybelater
* milestone: Future Release =>
Comment:
@johnjamesjacoby, @johnbillion, and I chatted about this ticket in #core-
multisite today.
I'm going to close this out as maybelater and reopen #21077 as a ticket to
introduce support for port numbers.
A couple opinions:
* Actually testing a IPv6 environment proved difficult. I wasn't able to
setup anything consistent in which I was confident that I was sending IPv6
requests and that the server was receiving and handling them properly.
Without clear guidelines for how to test any patches, we aren't going to
have the confidence necessary to merge.
* I'm not sure what the production use case is for supporting IPv6 as a
site domain. Multisite does not (to my knowledge) currently support IPv4
as a site domain either.
* Port numbers are a good first step and should prove to be immediately
useful for local environments (such as WordPress's) that use them.
If we reopen this in the future, it would be good to first establish a
clear use case and process for testing.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/15936#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list