[wp-trac] [WordPress Trac] #39586: Handle absolute request URI-s
WordPress Trac
noreply at wordpress.org
Tue Jan 17 01:09:06 UTC 2017
#39586: Handle absolute request URI-s
-------------------------------------+------------------------------
Reporter: szepe.viktor | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Rewrite Rules | Version: trunk
Severity: normal | Resolution:
Keywords: close reporter-feedback | Focuses:
-------------------------------------+------------------------------
Changes (by dd32):
* keywords: close => close reporter-feedback
Comment:
> This "circumstance" is the above mentioned standard.
I meant specific server configurations. Web servers normalise the incoming
request before providing it to PHP, most configurations would make `GET /`
(against example.com) and `GET http://example.com/` appear the same to the
application. WordPress supports `GET http://example.com/post-slug/`
properly when the web server in front of it sanitizes the incoming request
correctly.
Apache and Nginx both do this by default, unless you incorrectly configure
proxy functionality IIRC.
What server environment are you running under, and are there any specific
configuration settings in play?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/39586#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list