vbit
Forum Replies Created
-
Forum: Requests and Feedback
In reply to: HTTP_HOST redirect bugI have exactly the same problem behind our reverse-proxy or just to create different development environments based on ports on the same server.
We fixed a few things with more Apache rewriting rules and tricks but it’s getting complicated and we still have different problems.Ports and hosts for http and https should be considered as possible configuration variables if WordPress really have to rewrite url instead using bad assumptions!
Forum: Fixing WordPress
In reply to: Reverse Proxy and PermalinksI had nearly the same problem, here are my 2 cents:
It wasn’t so easy to determine which path was finally searched by WordPress at the end (I probably had to active Apache rewriting logs to find out… it’s a bit far now)Finally I fixed the problem with a symbolic link (on Unix system) named “blog” in my “blog” htdocs base directory.
Perhaps it’s easier to show the commands than to explain:
my url is http://www.domain.com/blog/ proxying to localhost:8080/ and I did
$ cd <path>/blog (that is the DocRoot of my Apache virtual host)
$ ln -s blog .Perhaps for you it will be a bit different because you have “~independence/blog” instead of “blog”
Try
a blog link at same level than you independence_dir (htdocs DocRoot) if possible (but looks like automatic web user dir..)
or
<>/independence_dir/blog/~independence/blog -> <>/independence_dir/blog )Having the final filepath wordpress is searching for will help you to guess what to do.
Anyway be careful, it’s quite dangerous because it can generate loops on some operations like if you try to copy the dir without special options!
I must say that the WP url rewriting features are still problematic when used in a complex web architecture like reverse-proxy.