John Steel wrote:
I've been using this pattern for some time with excellent results:
%
if (user == null) {
%
%@ include file=/jsp/loginpanel.jsp %
%
} else {
%
%@ include file=/jsp/logoutpanel.jsp %
%
}
%
I'm curious how this affects performance. In once
I've been using this pattern for some time with excellent results:
%
if (user == null) {
%
%@ include file=/jsp/loginpanel.jsp %
%
} else {
%
%@ include file=/jsp/logoutpanel.jsp %
%
}
%
I'm curious how this affects performance. In once sense, the assembled
jsp is
Hi,
I'm having a strange problem with my EJB over IIOP, in Resin 3.0 - I was
wondering if anyone might be able to give me some pointers, as I'm
thoroughly stuck now!
When I try to get the initial context, I get the following error in the
client:
javax.naming.ConfigurationException: MyEJBBean
John, check out resin's work directory for the source of the
resulting class to which your jsp becomes.
On Jun 1, 2007, at 3:35 AM, John Steel wrote:
I've been using this pattern for some time with excellent results:
%
if (user == null) {
%
%@ include file=/jsp/loginpanel.jsp %
%
With the SSL port set up in Resin, relative redirect on a https request
should go to the SSL port. Is that not the case?
Bill
On 6/1/07, Michael Fortin [EMAIL PROTECTED] wrote:
Hello,
We have our servers setup behind a load balancer and the load balancer
does all the encryption for ssl.
Hi Bill,
Thanks for the response. Honestly, I haven't tested it just yet. I
didn't see a 'secure' attribute on the http / config element so I just
wanted to confirm that 8443 will implicitly be secure even though I'm
not setting an encryption handler. I didn't see anything here
Hello,
We have our servers setup behind a load balancer and the load balancer
does all the encryption for ssl. All traffic inside our network is on
port 8080. If I do a relative redirect on a request from a secure url
it returns an insecure url. To try and fix this I setup another http
There is a secure-host-name under host
http://www.caucho.com/resin-3.0/config/resin.xtp#host
You may have to use that to set the port number for SSL.
Bill
On 6/1/07, Michael Fortin [EMAIL PROTECTED] wrote:
Hi Bill,
Thanks for the response. Honestly, I haven't tested it just yet. I
didn't
Hi Bill,
I've just tested my theory and it didn't work as I had hoped, the
request is not flaged as secure. In my resin.conf :
http server-id=web23-s1 host=172.30.1.219
virtual-host=www.ourdomain.com port=8080/
http server-id=web23-s1 host=172.30.1.219
virtual-host=www.ourdomain.com
Michael Fortin wrote:
How do I configure resin to know the request on 8443 is secure?
If your advanced load balancer can inject an HTTP header in the SSL
requests
you can use a servlet filter to add a request adapter that overrides the
isSecure method.
-Knut
We do have a header attribute that tells us if it's secure or not which
I could use in a filter. That would be an acceptable solution. I've
tried modifying the request in a filter before I tried setting up the
8443 port but isSecure is immutable. What do you mean by 'request
adapter'?
Resin 3.1.1 includes some features in rewrite-dispatch that may be able
to help:
http://www.caucho.com/resin-3.1/doc/rewrite-tags.xtp#set
Basically, there is facility to set the isSecure method of the request
to return true if there is some condition of the request (such as a
header set by the
12 matches
Mail list logo
