[Seaside] ReWrite Rule and css files - what am I doing wrong?

Brad Fuller brad at sonaural.com
Tue Feb 20 15:29:21 UTC 2007

Lukas Renggli wrote:
>> But, when looking at the apache access log there is:
>> GET /seaside/files/PRPierLibrary/style.css HTTP/1.1" 404 83
>> In the configuration page, PRPierLibary is in the File Library under
>> Pier.  But I don't know why there is css formating in the direct way
>> (http://www.my_domain.org:9999/seaside/pier), and apache is looking for
>> a css file in the second (http://www.my_domain.org/).
> That's the new way for Seaside to serve static files.

Ok, but why am I getting css formating correctly w/o using apache? There 
were no css files for seaside to access.

>> BTW: I did create a sub-directory called: files/PRPierLibrary with the
>> default style.css from Lukas under the directory where the image is
>> located, but that didn't do anything.
>> (I stopped and restarted WAKom just in case.)
> You either need to create a directory seaside/files/PRPierLibrary/
> with your files 

note to others:

the directory that houses your css files:


must be a subdir under your document root for apache to access it.

>or add the following rewrite rule right after enabling
> the rewrite engine:
> RewriteRule ^/seaside/files/PRPierLibrary/(*.)$
> http://www.my_domain.org:9999//seaside/files/PRPierLibrary/$1 [P,L]
> Cheers,
> Lukas

brad fuller
  +1 (408) 799-6124

More information about the Seaside mailing list