[wp-trac] [WordPress Trac] #3987: IPv6 support

[WordPress Trac]

#3987: IPv6 support
----------------------------+-----------------------------------------------
 Reporter:  xiand0          |       Owner:  anonymous
     Type:  defect          |      Status:  new      
 Priority:  normal          |   Milestone:  2.3      
Component:  Administration  |     Version:  2.2      
 Severity:  minor           |    Keywords:  IPv6     
----------------------------+-----------------------------------------------
 WordPress (MU at least) works just fine with IPv6, you can signup, login,
 blog, post, everything works, except for some minor issues.

 For example, when a IPv6 user posts a comment their IP is (supposedly)
 2001618400012, not 2001:0618:0400:0120:0000:0000:0000:0000 or something
 like that (which it really is). So WP/WPMU doesn't understand when : is a
 part of the IP, and also cuts off such IPs - who are generally way longer
 than a IPv4 IP (IPv6 have eight sections of four, seperated by :).

 Now, as said, IPv6 works - but there are these minor issues. It's not the
 end of the world that the IP WP sees is WRONG (or just a part of the IP),
 but it's worth fixing.

 Also, one thing to keep in mind:

 The Wiki system MediaWiki used to work with IPv6. Version up to version
 1.8.4 works just fine with IPv6. Then the developers changed some code and
 MediaWiki version 1.9.X is TOTALLY BROKEN with IPv6 - MW version 1.9.x
 breaks when IPv6 users VISIT the site (As in Try to view a page..). This
 is extremely serious and completely rules out using MW version higher than
 1.8.x.

 This is highly relevant to WordPress: People are using both WordPress and
 WPMU on IPv6-enabled hosts, IPv6 users are visiting them, and it works, so
 do keep this in mind when adding new code and changing old code: Make sure
 new code don't suddenly break every WP installation out there which is
 IPv6 enabled.

 The MediaWiki story is relevant because Code which works with IPv4
 generally also works with IPv6, but some (poorly written) code doesn't,
 and MW managed to completely break (breaks when you try to view a page,
 I'd say that's completely broken) their software because they wrote some
 code which only worked if the IP contained a dot . in it and added that to
 a later version. So.. make sure you don't do that.

 And consider changing the code which grabs the IP, as said, I've noticed
 that comments are shown to come from IP 2001618400012, not
 2001:0618:0400:0120:0000:0000:0000:0000, I haven't looked into what
 function grabs the IP to be used there, but if the same code is used
 elsewhere then it may cause problems for other parts of WP now - or in the
 future.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/3987>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software