[wp-trac] [WordPress Trac] #17048: URLs delivered to the browser should be root-relative
WordPress Trac
wp-trac at lists.automattic.com
Tue Aug 16 16:56:27 UTC 2011
#17048: URLs delivered to the browser should be root-relative
--------------------------+-----------------------
Reporter: dmole | Owner: edwardw
Type: defect (bug) | Status: reopened
Priority: normal | Milestone:
Component: General | Version: 3.1
Severity: normal | Resolution:
Keywords: |
--------------------------+-----------------------
Comment (by dmole):
edwardw you deserve respect for you work and tolerance. Hopefully, like
all the others in this thread, azaozz will come to respectfully attempt to
address this bug, I'm sure he was just to busy to properly take the time
to understand and address this bug.
Replying to [comment:21 edwardw]:
Hi edwardw, you only used wget with one domain/ip so that's not really a
test of of your good work :) this is what I get:
{{{
wget http://127.0.0.1/wordpress/wp-admin/ -O /dev/null
--2011-08-16 12:27:03-- http://127.0.0.1/wordpress/wp-admin/
Connecting to 127.0.0.1:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://my.domain.tld/wordpress/wp-
login.php?redirect_to=http%3A%2F%2F127.0.0.1%2Fwordpress%2Fwp-
admin%2F&reauth=1 [following]
--2011-08-16 12:27:05-- http://my.domain.tld/wordpress/wp-
login.php?redirect_to=http%3A%2F%2F127.0.0.1%2Fwordpress%2Fwp-
admin%2F&reauth=1
Resolving my.domain.tld... 55.155.155.155
Connecting to my.domain.tld|55.155.155.155|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1943 (1.9K) [text/html]
Saving to: `/dev/null'
100%[====================================================================================================================================================================================================================================>]
1,943 --.-K/s in 0s
2011-08-16 12:27:06 (77.3 MB/s) - `/dev/null' saved [1943/1943]
}}}
and
{{{
wget http://my.domain.tld/wordpress/wp-admin/ -O /dev/null
--2011-08-16 12:29:09-- http://my.domain.tld/wordpress/wp-admin/
Resolving my.domain.tld... 55.155.155.155
Connecting to my.domain.tld|55.155.155.155|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://my.domain.tld/wordpress/wp-
login.php?redirect_to=http%3A%2F%2Fmy.domain.tld%2Fwordpress%2Fwp-
admin%2F&reauth=1 [following]
--2011-08-16 12:29:10-- http://my.domain.tld/wordpress/wp-
login.php?redirect_to=http%3A%2F%2Fmy.domain.tld%2Fwordpress%2Fwp-
admin%2F&reauth=1
Connecting to my.domain.tld|55.155.155.155|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1943 (1.9K) [text/html]
Saving to: `/dev/null'
100%[====================================================================================================================================================================================================================================>]
1,943 --.-K/s in 0s
2011-08-16 12:29:10 (101 MB/s) - `/dev/null' saved [1943/1943]
}}}
Replying to [comment:22 azaozz]:
>...I don't see any compelling user case that requires it to change. The
user case ... is very rare and should preferably be handled in .htaccess
or web.config...
azaozz, thanks for the input but I don't think you understand the use case
because the problem can't be addressed with apache config. Additionally
NAT, sub nets, multiple IPs, and multiple domains are anything but "rare".
Obviously it not rare but imposable for users to use a vanilla WordPress
site from with more than one domain, that is the reason for this bug
report. (If I'm wrong or missing something please educate us) My opinion
is that the FSM would love if people gave solid support for there
"opinions".
Clarification:The objective is to make a vanilla WordPress site work from
more than one URL ip/domain/port.
ps azaozz can you link us to an online log of the wp-hackers mailing list?
(in case we get kicked out of here)
--
Ticket URL: <http://core.trac.wordpress.org/ticket/17048#comment:26>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list