-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
Mark Thomas wrote:
That looks like a bug to me. Please add to to bugzilla so it doesn't get
lost and forgotten about.
Done. Thanks.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45997
- -chris
-BEGIN PGP SIGNATURE-
Version:
Christopher Schultz wrote:
Chuck,
Caldarale, Charles R wrote:
The code in 6.0 is noticeably different from that in 5.5 for protocol
initialization, including setting up the socket factory. Would it be
possible to test the config on 6.0 to see if you can achieve the
desired results there?
.
Date: Sat, 11 Oct 2008 13:53:46 +0100
From: [EMAIL PROTECTED]
To: users@tomcat.apache.org
Subject: Re: Non-secure HTTP connector with secure=true requires a
keystore?
Christopher Schultz wrote:
Chuck,
Caldarale, Charles R wrote:
The code in 6.0 is noticeably different from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
Peter Rossbach wrote:
As you want SSL enabled, you must add schema=https secure=true
SSLEnabled=true
at your config.
No, I don't want SSL enabled. I want Tomcat to NOT do SSL, but I want it
to report to my application that SSL is being
No, I don't want SSL enabled. I want Tomcat to NOT do SSL, but I want it
to report to my application that SSL is being used.
So you want quality software to lie to you? It would be a bug if Tomcat
said it was secure when it's not, and it sounds pretty goofy to want it.
The deal is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
secure=... corresponds to request.isSecure
I have not found this to be entirely true. Please see my original post.
If secure=true merely sets the return value for request.isSecure, then
I should not need a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Wall wrote:
No, I don't want SSL enabled. I want Tomcat to NOT do SSL, but I want it
to report to my application that SSL is being used.
So you want quality software to lie to you? It would be a bug if Tomcat
said it was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
The code in 6.0 is noticeably different from that in 5.5 for protocol
initialization, including setting up the socket factory. Would it be
possible to test the config on 6.0 to see if you can achieve the
Same here. I terminate all SSL in a load balancer and forward in the
clear back to 8080 or 8081. Application code is peppered non-standard
calls to see things set by a filter to see if it's considered secure
even though Tomcat thinks otherwise. In the more extreme case, I
could consider
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: Non-secure HTTP connector with secure=true
requires a keystore?
Successful startup. Using HTTP, a test JSP reports that
request.isSecure() returns true, which is exactly what
Filip claims. It appears that the behavior of TC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: Non-secure HTTP connector with secure=true
requires a keystore?
I would have expected 5.5 to act like 6.0.
An odd assumption...
Perhaps I
=true
at your config.
Peter
Am 07.10.2008 um 21:01 schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: Non-secure HTTP connector with secure=true requires
a keystore?
I
21:01 schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: Non-secure HTTP connector with secure=true requires
a keystore?
I tried it with scheme=http at first, and got
I'm trying to configure an HTTP Connector that reports to the
application that the connection is secure. According to the TC
documentation
(http://tomcat.apache.org/tomcat-5.5-doc/config/http.html), you should
be able to simply set:
secure=true
in the Connector and all should be well.
Yes,
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Non-secure HTTP connector with secure=true
requires a keystore?
I'm trying to configure an HTTP Connector that reports to the
application that the connection is secure.
I thought I had done this using just what you described
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
I thought I had done this using just what you described, but it may
have been in 6.0. Can you post the config for the Connector in
question? Have you left the scheme set to HTTP?
Yup. Here's the configuration:
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: Non-secure HTTP connector with secure=true
requires a keystore?
I tried it with scheme=http at first, and got the same exception.
The code in 6.0 is noticeably different from that in 5.5 for protocol
initialization, including
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: Non-secure HTTP connector with secure=true requires
a keystore?
I tried it with scheme=http at first, and got the same exception.
The code
18 matches
Mail list logo
