Prevent proxying of static assets

[Gary Doades]

If you can't use rewite rules for some reason, proxying works just
fine. The setup instructions currently state that getting apache to
serve static files is a problem in this case. However, the following
example will prevent proxying of the static assets for a standard
rails application.

Inside a VirtualHost perhaps.....

DocumentRoot "/usr/home/myuser/myapp/public"
ServerName www.myapp.com
ProxyPass /javascripts !
ProxyPass /images !
ProxyPass /stylesheets !
ProxyPass / http://127.0.0.1:8080/myapp/
ProxyPassReverse / http://127.0.0.1:8080/myapp/
<Directory "/usr/home/myuser/myapp/public">
Options FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
</Directory>


This assumes that myapp has been setup on switchpipe that is running
on port 8080

Cheers,
Gary.

[Peter Cooper]

On Apr 15, 2:48 pm, Gary Doades <g...@gpdnet.co.uk> wrote:
> If you can't use rewite rules for some reason, proxying works just
> fine. The setup instructions currently state that getting apache to
> serve static files is a problem in this case. However, the following
> example will prevent proxying of the static assets for a standard
> rails application.

That is a really cool example you've given; thanks! I didn't realize
you could do that with ProxyPass.

Cheers,
Peter Cooper

[Gary Doades]

It just seems simpler than using rewrite rules (to me).

Testing on FreeBSD 7.0 64 bit platform, Xeon 2.33 Mhz dual core, this
arrangement only seems to add about 1ms overhead using Switchpipe as
opposed to just sending the request to a mongrel instance alone.

Using rewrite with .htaccess files uses about twice that. Don't know
if that's the rewrite overhead or having to process .htaccess though.

Cheers,
Gary.

[Peter Cooper]

> Testing on FreeBSD 7.0 64 bit platform, Xeon 2.33 Mhz dual core, this
> arrangement only seems to add about 1ms overhead using Switchpipe as
> opposed to just sending the request to a mongrel instance alone.
>
> Using rewrite with .htaccess files uses about twice that. Don't know
> if that's the rewrite overhead or having to process .htaccess though.

Or both. Even though .htaccess will be in file cache, it'll still add
time, and being prepared to deal with regular expressions will keep
rewrites a little slower too. I will try and update the documentation
with your example for those who are interested :) (Once I play with it
myself, of course - I have something your tips might suit deployed
live now with rewrite rules..)

Cheers,
Pete