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

20 Feb 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.

  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 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] 
(I moved this to the Pier ML as I think it's Pier related, sorry if this 
is confusing - don't want to bother others)

Thanks Lukas.

Along those same lines, I'm getting long lines after the domain name 
when I select a link in Pier. Is this correct?

information/license?command=PRViewCommand&view=PRDefaultView&_k=swboZglt&29&_n&_s=MELVlGoXVospTlDw

?command=PRViewCommand&view=PRDefaultView&_k=zYTOouCP&21&_n&_s=MELVlGoXVospTlDw

information/license?command=PRViewCommand&view=PRDefaultView&_k=rKYbypAd&25&_n&_s=MELVlGoXVospTlDw

seems like it should be shorter.. they are shorter in my other seaside 
app, although, it's not Pier.