[wp-trac] [WordPress Trac] #21077: Add support for custom ports in multisite site addresses

[WordPress Trac]

#21077: Add support for custom ports in multisite site addresses
------------------------------------------+-----------------------------
 Reporter:  djzone                        |       Owner:  (none)
     Type:  enhancement                   |      Status:  reopened
 Priority:  normal                        |   Milestone:  Future Release
Component:  Bootstrap/Load                |     Version:  3.4
 Severity:  normal                        |  Resolution:
 Keywords:  needs-patch needs-unit-tests  |     Focuses:  multisite
------------------------------------------+-----------------------------

Comment (by johnjamesjacoby):

 > Should all port numbers be allowed or should there be a filtered list?

 I think all port numbers should be allowed.

 Story time. Yesterday I had to switch back to using MAMP PRO for local
 stuff. It makes both Apache and Nginx web servers available, both with
 `http` and `https` schemes, all on different ports. Depending on my
 /etc/hosts setup, depending on WordPress constants and options being
 filtered, depending on what I'm working on or testing, it's pretty
 convenient to have WordPress available on so many different ports.

 MAMP has its own default ports but you can easily use 80/443/81/7443, or
 whatever you want really. The ability to use any port numbers is useful if
 you also have Docker/Lando running, or have Local running, or Valet,
 etc... especially when transitioning between environments.

 I assume it would also be really useful with running multiple instances of
 something like VVV.

 Lastly, ports are valid URL segments, even if they are weird to see. IMO,
 that means there is some inherent obligation to support them.

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