Inverse proxy breaks permalinks

[Bernhard Reiter]

I have a WP installation at my university's webspace (on an apache server), say ​http://myuni.ac.at/mydir/wordpress/ , and an inverse proxy domain ​http://mydomain.at/ for it.
This means that any request to the latter, eg for ​http://mydomain.at/2009/02/12/inverse-proxy-trouble/ , is forwarded to ​http://myuni.ac.at/mydir/wordpress/ , 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 ​http://mydomain.at/ (siteurl is set to ​http://myuni.ac.at/mydir/wordpress/ -- 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

wp-includes/classes.php
in function parse_request: change line 162 from

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

to

$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.

[Denis-de-Bernardy]

please be so kind to give the attached patch a try

[Denis-de-Bernardy]

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

[Denis-de-Bernardy]

no tests in 2 weeks, punting to 2.9

[dd32]

Punting to Future Release due to no traction.

[chriscct7]

Still needs unit tests and a refresh