[wp-trac] [WordPress Trac] #17047: Not following spec for REQUEST_URI
WordPress Trac
wp-trac at lists.automattic.com
Tue Apr 5 03:18:18 UTC 2011
#17047: Not following spec for REQUEST_URI
---------------------------+------------------------------
Reporter: sterlo | Owner: sterlo
Type: defect (bug) | Status: reviewing
Priority: normal | Milestone: Awaiting Review
Component: Rewrite Rules | Version: 3.1
Severity: normal | Resolution:
Keywords: has-patch |
---------------------------+------------------------------
Comment (by sterlo):
Replying to [comment:3 nacin]:
> I figured we already had this fix, but I've also never seen a server do
this. Is this really seen outside of the spec?
I popped into the Apache IRC channel, and said "What causes the
REQUEST_URI to have a full path", I was then bombarded with responses
like: "Someone is attempting to do a proxy."
So I would say that it's a common thing.
I work with another developer who loves to RTFM and he's the one who
pointed out it was actually against the spec, and not just a local
problem.
We tested this using the latest from the subversion trunk - the problem
still existed.
It's very easy to test against, just get the IP of your server and do:
{{{
curl -sv -x YOURIP:80 "http://YOURWEBSITE.TLD/" -o /dev/null
}}}
You'll see the problem manifest.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/17047#comment:4>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list