[wp-trac] Re: [WordPress Trac] #10045: fsockopen() fails connecting to localhost when the server contains a ipv6 hosts entry

WordPress Trac wp-trac at lists.automattic.com
Sat Jun 6 10:58:56 GMT 2009


#10045: fsockopen() fails connecting to localhost when the server contains a ipv6
hosts entry
--------------------------+-------------------------------------------------
 Reporter:  dd32          |       Owner:  dd32     
     Type:  defect (bug)  |      Status:  new      
 Priority:  normal        |   Milestone:  2.8      
Component:  HTTP          |     Version:  2.8      
 Severity:  normal        |    Keywords:  has-patch
--------------------------+-------------------------------------------------

Comment(by dd32):

 There are side effects, Some security software blocks if attempts are made
 to connect to the loopback instead of wan interface.

 This doesnt affect most users, it only affects people who run a blog on
 the localhost, that is, have the site url set to localhost.

 On a production server, WordPress doesnt connect to 'localhost' instead it
 connected to 'real.fqdn.whatever' which resolves to 123.123.123.123. which
 has no problem.

 *This doesnt affect those on a load balancer. This doesnt affect those
 running live servers, This affects nearly no end users. It only affects
 developers*

 Its common for desktop setups to include a IPv6 loopback definition in the
 hosts file, Eg, Vista:
 {{{
 127.0.0.1       localhost
 ::1             localhost
 }}}

 If someones running a blog on localhost, mainly for dev work, and is using
 fsockopen HTTP transport (Which will be 99.9% of us now that #9998 has
 changed the order) then there'll be Cron issues.

 Previously most installs didn't use the fsockopen transport, all the other
 transports dont have this problem with the loopback dns.

 I have a feeling that code very similar to this existed in the pre-http-
 api days, to solve this exact problem.

 This  can wait until early in 2.9 if need be, It'll probably be needed
 when everyone starts complaining in about 48 hours.. ;)

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/10045#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list