Changes between Initial Version and Version 32 of Ticket #15936
- Timestamp:
- 12/23/2018 01:55:40 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15936
-
Property
Status
changed from
new
toassigned
- Property Focuses multisite added
-
Property
Severity
changed from
normal
tomajor
- Property Cc mitcho@… info@… micahwave added
-
Property
Component
changed from
General
toNetworks and Sites
- Property Owner set to jeremyfelt
-
Property
Version
changed from
3.0.3
to3.0
-
Property
Milestone
changed from
Awaiting Review
toFuture Release
- Property Keywords has-patch dev-feedback 2nd-opinion added
-
Property
Type
changed from
defect (bug)
toenhancement
-
Property
Status
changed from
-
Ticket #15936 – Description
initial v32 2 2 It tries to handle the URL as it as if there were a port appended, but then fails to strip it off. Incidentally the error message here: 'Multisite only works without the port number in the URL.' is untrue, since ports are handled (but for only two particular cases, port 80 and 443). 3 3 4 The attached patch, against Word press 3.0.3, fixes both these issues, and allows ports other than 80 and 443 to be used with Wordpress, by just stripping off the trailing port rather than special-casing the two well-known ports, and not incorrectly detecting IPv6 literals as URLs with ports in. It also has the advantage of being much more compact.4 The attached patch, against WordPress 3.0.3, fixes both these issues, and allows ports other than 80 and 443 to be used with Wordpress, by just stripping off the trailing port rather than special-casing the two well-known ports, and not incorrectly detecting IPv6 literals as URLs with ports in. It also has the advantage of being much more compact. 5 5 6 6 It may be worth someone thinking through whether the substitution is strictly correct with reference to the URL standards, but I'm pretty sure that this is an improvement on the current code.