<LocationMatch .*\.nocache\..*>
ExpiresActive On
ExpiresDefault “access”
</LocationMatch>

<LocationMatch .*\.cache\..*>
ExpiresActive On
ExpiresDefault “now plus 1 year”
</LocationMatch>

Previous to that I tried the following with no success:

<Files *.nocache.*>
ExpiresActive On
ExpiresDefault “access”
</Files>

<Files *.cache.*>
ExpiresActive On
ExpiresDefault “now plus 1 year”
</Files>

On ServerA I have the following in /var/www/html/.htaccess:

## EXPIRES CACHING ##
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg “access plus 1 year”
ExpiresByType image/jpeg “access plus 1 year”
ExpiresByType image/gif “access plus 1 year”
ExpiresByType image/png “access plus 1 year”
ExpiresByType text/css “access plus 1 month”
ExpiresByType application/pdf “access plus 1 month”
ExpiresByType text/x-javascript “access plus 1 month”
ExpiresByType application/x-shockwave-flash “access plus 1 month”
ExpiresByType image/x-icon “access plus 1 year”
ExpiresDefault “access plus 2 days”
</IfModule>
## EXPIRES CACHING ##

To the best of my knowledge Proxy has the correct configurations in httpd.conf to permit browser caching as does the .htaccess file on ServerA where SiteA lives. Testing SiteA with various web tools reports that browser caching is not enabled. I am hoping fervently that someone has experience with this sort of setup and can help point me in the right direction. Thank you in advance!

I’ve installed WordPress on a server under /my_blog/ it is configured to work as https://www.mysite.com/blog1/

Now, www.mysite.com points to a different server. This has Apache with mod_proxy and I’ve added the following line to httpd.conf

ProxyPass /blog1 https://192.168.100.60/my_blog

But whenever I hit https://www.mysite.com/blog1/ I get the “Nothing found for My_blog” error. Do I need to hack something in order to get this working?

Contents of .htaccess on the 192.168.100.60/my_blog/

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /my_blog/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /my_blog/index.php [L]
</IfModule>

# END WordPress

1) We have several sites at different domains (foo.com, bar.com, etc.com) that use Ruby on Rails and Apache (already working).

2) We would like to use Apache’s mod_proxy to make foo.com/blog, bar.com/blog, and etc.com/blog all point to our WP VPS at wpblog.com/blog (also, already set up and working)

3) We would like these WP instances to be a single WP_ALLOW_MULTISITE installation that runs from that location and is domain-mapped to serve these domains as separate subdirectory installations.

Has anyone ever done something like this, using domain mapping?

I’m trying to run several websites for myself, one of them being wordpress, off of one IP. After Googling around a bit I found the mod_proxy for Apache which will let me do this. My endgame is to have something like this:
|—> Server 1
[internet]–>[proxy host]—+—> WordPress
|—> Server 2
|—> Server 3

Each server is listening to ports 80 and 443. Here is what I have to proxy things to the WordPress server:

NameVirtualHost *:80
NameVirtualHost *:443

<VirtualHost *:80>
        ServerName SERVER_URL
        ProxyPreserveHost On
        ProxyPass / https://1.2.3.4/
        ProxyPassReverse / https://1.2.3.4/
</VirtualHost>

#<VirtualHost *:443>
#        ServerName SERVER_URL
#        ProxyPreserveHost On
#        ProxyPass / https://1.2.3.4
#        ProxyPassReverse / https://1.2.3.4
#</VirtualHost>

The SSL-secured site has been disabled for now until I can figure out how to proxy the SSL propery (some help in this area wouldn’t be unappreciated, but the main goal is I’d like to have a working site first.)

Note: The configs above have been sanitized

A very quick and probably really easy feature request:

I am running WordPress behind a reverse proxy. Therefore, it would be really nice if comments could log the IP from the X-Forwarded-For header if it is set.

Thanks

– Nils