19 Mar
2007
19 Mar
'07
9:47 p.m.
Lukas Renggli wrote:
OK, I admit this is a bit OT, but it does have something to do with
getting Seaside and Apache working together. Others might benefit too...
and I'm surprised that others don't see this problem.
Actually, one would think that the solution above would work, but in my
case it does not. In fact, sometimes I get the path repeated 3 times!
What I did was bypass apache, set the Pier app default timeout low and
go at it to see if I could find something useful. In every case of a
timeout, Pier worked fine when bypassing apache. After timeouts, seaside
went to the next page just fine. So, I think my issue is something to do
with apache. I thought maybe there is a cache problem on the server
side, so I made sure that no cache module is loaded. Why would the path
get duplicated so many times and KOM/Seaside work just fine?
brad
I get
error's like this sometimes when I click a link in pier:
Error: "/seaside/mmiki/seaside/mmiki/A-Page" not found.
Notice the path is duplicated. I figure that this is an error that
occurs after the page time's out. yes?
How can I fix this? Why does this happen? Lukas mentioned a thread to
search for but I can't find that message (sorry!) and I haven't
found a
good explanation.
Can anyone point me in the right direction?
Again this can be solved with a RewrtieRule that you put before
RewriteCond in your Apache config:
RewriteRule $/seaside/mmiki/(.*)^ http://localhost:9999/$1
[proxy,last]
The reason you need this is a problem of Seaside redirecting to the
wrong URL when a session has a timeout. Unfortunately this is not
that easy to fix. I did several attempts during the development of
2.7, but could not figure out a way that did not break a lot of other
applications altogether. Anyway, for now the above RewriteRule does
the trick.