16 Mar
2007
16 Mar
'07
4:42 a.m.
Brad Fuller wrote:
Believe it or not, I worked on this all day. The rewrite rules you have
are correct and work for me... at the end of the day. I do not know why
they didn't work right off the bat. When I tried them and they didn't
work, I tried various other tricks and studied the rewrite rules and
conditions on the apache page and elsewhere. Nothing really worked well.
Then, the seaside image started hanging by the end of the day (don't
know why, I didn't touch it much) and I finally had to just kill it. At
that point I was actually back to where I started but I didn't know I
had re-written the rules back to Lukas's original suggestion! After I
restarted seaside, it just worked. Go figur.... What a day. (hey, I know
more about rewrite rules...)
Now... my next problem is the timeout problem. When the page time's out,
I get an error. At least I think that's the reason. I'll create another
thread for that discussion.
Everyone, thanks for your help!
brad
Yes it looks
to me as if the files do not get rewritten correctly.
Try adding the following line to your rewrite rules:
RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/
files/$1 [proxy,last]
Make sure it is the first rule to be applied, so that it looks
somehow like:
ProxyPreserveHost On
RewriteEngine On
RewriteRule ^/seaside/files/(.*)$ http://localhost:9999/seaside/
files/$1 [proxy,last]
RewriteCond /home/web/mmiki/%{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ http://localhost:9999/seaside/mmiki/$1
[proxy,last]
Thanks Lukas. I'm learning more about rewrite rules than I ever wanted
to! That almost works. It now doesn't accommodate css files served from
apache. Why it worked before, I don't know, but I'll find out. I'm
investigating it now and I'll post my results. Hopefully, others might
find it useful.