Re: T5 application behaviour behind an apache web server

2008-08-06 Thread Peter Stavrinides
goris Ioannou" <[EMAIL PROTECTED]> To: "Tapestry users" Sent: Friday, 1 August, 2008 11:25:38 AM GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: T5 application behaviour behind an apache web server Hi all, I'm facing this peculiar behavior in my T5 application: I

Re: T5 application behaviour behind an apache web server

2008-08-04 Thread Grigoris Ioannou
Finally this solved the problem: I used both of your suggestions: I replaced ROOT.war with my application and I set "tapestry.suppress-redirect-from-action-requests" to true This seems to solve the problem. Thanks, Grigoris On Fri, Aug 1, 2008 at 4:18 PM, Jonathan Barker <[EMAIL PROTECTED] > wr

RE: T5 application behaviour behind an apache web server

2008-08-01 Thread Jonathan Barker
ECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Grigoris > Ioannou > Sent: Friday, August 01, 2008 04:26 > To: Tapestry users > Subject: T5 application behaviour behind an apache web server > > Hi all, > > I'm facing this peculiar behavior in my T5 application: > > I h

Re: T5 application behaviour behind an apache web server

2008-08-01 Thread Carl Crowder
I've had a similar problem. It's because when Jetty redirects you, it uses "request.getServerName()" and the request context to create a complete URL. So if you go to your app at "http://localhost/page";, and that sends a redirect, Jetty will redirect you to "http://localhost/whatever";. The prob