s="75"
> enableLookups="false" redirectPort="8443" acceptCount="100"
> connectionTimeout="2" disableUploadTimeout="true" >
>
>allow="xxxx" deny=""/>
&g
te annotation... try removing the extra "s" ?
>
>
> On Mon, 19 Sep 2011 20:44:13 +0200, Michael Molloy
> wrote:
>
>> I will look into this because I'm getting desperate. If I can't get this to
>> work, I'm going to have to rewrite the app using
ed you can instead set the "Host" header on the backend
> request by setting "ProxyPreserveHost On" in httpd.conf. With that setting,
> Apache will use the "Host" header from the original request when
> communicating with the backend.
>
> Also, if yo
Just reread this email from Denis, and I do understand the need for the full
URL. Thank you, Denis.
I still don't understand why my implementation of BaseURLSource isn't working,
however.
--Michael
On Sep 19, 2011, at 4:26 AM, Denis Delangle wrote:
> Hello,
>
> As https is managed by your lo
nfiguration.add(BaseURLSource.class, source);
}
--Michael
On Sep 19, 2011, at 10:49 AM, Lenny Primak wrote:
> If your load balancer handles all of your SSL, you should not worry at all
> about secureEnabled (disable it)
> and it should all work like a champ.
>
> On Sep 19, 2011, at 11:08 AM, Michael Molloy wrote:
>
where there is
> no support for X-Forwarded-* headers, you can use this servlet filter instead:
> http://code.google.com/p/xebia-france/wiki/XForwardedFilter
>
> Martin
>
> On Mon, 19 Sep 2011 16:29:17 +0200, Michael Molloy
> wrote:
>
>> Unfortunately, the Apache e
The line
>
is commented out in server.xml, so I think you're right, it is the standard
HTTP listener connector.
So is there something on the Tomcat side that needs to change, or is it on the
Apache side?
--Michael
On Sep 19, 2011, at 9:52 AM, Robert Zeigler wrote:
> Looks like you're not
AJP protocol to communicate between apache and Tomcat.
> What's your communication medium between apache and tomcat?
>
> On Sep 19, 2011, at 1:50 AM, Michael Molloy wrote:
>
>> I have my first Tapestry application ready for production, but I'm having
>> some probl
Thanks, I was too sleepy (and desperate) to remember that last night. There is
no SSL going on between the apache server and the tomcat server.
Concerning the proxy link you listed below, there are already several
production non-Tapestry apps running in this configuration, and none of them
have
One other thought. Looking over the http://tapestry.apache.org/https.html page
again, I notice that it is saying there is a need for that method if your
application has some pages that are secure and others that are not. In my case,
all of mine are secure, so I would think I could just use relat
I have my first Tapestry application ready for production, but I'm having some
problems, and I think it is Tapestry rather than Apache.
We have hardware load balancers sitting in front of two apache httpd servers.
The apache servers sit in front of 4 tomcat servers. SSL is handled by the load
b
11 matches
Mail list logo
