Make WordPress Core

Opened 15 years ago

Last modified 2 months ago

#9102 assigned defect (bug)

Inverse proxy breaks permalinks

Reported by: bernhard-reiter's profile Bernhard Reiter Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 2.7
Component: Permalinks Keywords: has-patch needs-testing needs-unit-tests early needs-refresh
Focuses: Cc:


I have a WP installation at my university's webspace (on an apache server), say , and an inverse proxy domain for it.
This means that any request to the latter, eg for , is forwarded to , which in turn means that the REQUEST_URI there becomes /mydir/wordpress/2009/02/inverse-proxy-trouble/ . My home variable is of course set to (siteurl is set to -- otherwise I wouldn't be able to login to WP).

Unfortunately, when analyzing REQUEST_URI, wordpress chops off the home path, not the siteurl one. This may be okay for some purposes, but in the inverse proxy case, permalinks break. For a fix, I had to hack two wordpress core files, namely

in function parse_request: change line 162 from

$home_path = parse_url(get_option('home'));


$home_path = parse_url(get_option('siteurl'));

and wp-includes/rewrite.php, in function get_pagenum_link, line 987, same modification.

This is a dirty hack, of course; so I wonder if in general, using the siteurl path is valid in any case where the home host differs from the siteurl host. If so, I suggest changing the affected files in such a manner.

Attachments (1)

9102.diff (2.4 KB) - added by Denis-de-Bernardy 15 years ago.

Download all attachments as: .zip

Change History (9)

#1 @Bernhard Reiter
15 years ago

  • Cc Bernhard Reiter added

#2 @Denis-de-Bernardy
15 years ago

  • Keywords has-patch needs-testing added; inverse proxy permalinks removed

please be so kind to give the attached patch a try

#3 @Denis-de-Bernardy
15 years ago

  • Keywords 2nd-opinion added

this might be a bit too big a change for a nearby release.

#4 @Denis-de-Bernardy
15 years ago

  • Keywords early added; 2nd-opinion removed
  • Milestone changed from 2.8 to 2.9

no tests in 2 weeks, punting to 2.9

#5 @ryan
14 years ago

  • Milestone changed from 2.9 to 3.0

#6 @dd32
14 years ago

  • Milestone changed from 3.0 to Future Release

Punting to Future Release due to no traction.

#7 @ryan
10 years ago

  • Owner ryan deleted
  • Status changed from new to assigned

#8 @chriscct7
9 years ago

  • Keywords needs-unit-tests needs-refresh added

Still needs unit tests and a refresh

Note: See TracTickets for help on using tickets.