Try to add proxyName e proxyPort params to your tomcat's connector configuration (server.xml) like here :
<Connector port="81" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" debug="0" connectionTimeout="20000" disableUploadTimeout="true" proxyName="liferay.archeometra.it <http://liferay.archeometra.it>" proxyPort="80" /> Paolo On 10/12/05, Kevin Menard <[EMAIL PROTECTED]> wrote: > > On Wed, 12 Oct 2005 11:20:55 -0400, Petri Wessman <[EMAIL PROTECTED]> wrote: > > > Hello all, I'm writing an app with the new Tapestry (version 4 beta 10 > > at the moment), and so far love the changes -- so much nicer and cleaner > > that Tapestry 3. > > > > However, I just ran into a problem. I tried deploying the app on the > > to-be production server with an Apache frontend, I've been using direct > > JBoss access to port 8080 so far. No luck, reverse proxying refused to > > work, Tapestry kept directing me to port 8080 even though I had > > specified ProxyPassReverse to Apache. > > I ran into this too. I decided to just go with mod_jk, which took care of > the problem. I do wonder if this will still work in Apache httpd 2.1, > which makes mod_jk an enhancement to mod_proxy. > > -- > Kevin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
