[wp-trac] [WordPress Trac] #17048: URLs delivered to the browser should be root-relative (was: urls deliverd to the browser should be root-relative)

[WordPress Trac]

#17048: URLs delivered to the browser should be root-relative
--------------------------+------------------------------
 Reporter:  dmole         |       Owner:  edwardw
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  3.1
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |
--------------------------+------------------------------
Changes (by edwardw):

 * keywords:   => dev-feedback
 * owner:   => edwardw
 * status:  new => accepted


Comment:

 I would have to agree here. Many other pieces of PHP or ASP.NET software
 run fine when the domain name is different from what the application is
 installed to - the issue here is that it is the same server but just using
 multiple interfaces (IP addresses, NAT gateways, reverse proxies, and so
 forth). For example, if I have my development test WP server running at
 http://localhost/ with IP 192.168.1.1, then when I visit it on another
 computer with http://192.168.1.1/ all the links are absolute to
 http://localhost/, resulting in things like
 http://localhost/wordpress/?feed=rss2 that don't resolve on the other
 computer. This means all images, links and CSS are completely broken. In
 addition, many networks involve reverse proxies and NAT gateways (e.g.
 outside may see http://blog.example.com/ but employee sees
 http://wordpress.servers.example.com/ or something like that).

 I think that this feature would make WordPress a more robust and tolerant
 software. If there is no significant opposition I will working on a
 solution to this problem.

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