Peter,
On 8/11/22 17:00, Peter Kreuser wrote:
I have tried all the fancy new cert options and they are cool.
And I do agree that it's more readable.
What would be useful would be one sample how to transfer a simple "old" config
to SSLHostConfig.
Let's see if a PNG attachment makes it to the
ware | Infrastructure Solutions
> >
> > 8080 Cobblestone Rd | Urbandale, IA 50322
> > MAC: F4469-010
> > Tel 515-988-2508 | Cell 515-988-2508
> >
> > jonmcalexan...@wellsfargo.com
> > This message may contain confidential and/or privileged information. If you
>
On 11/08/2022 22:00, Peter Kreuser wrote:
What would be useful would be one sample how to transfer a simple "old" config
to SSLHostConfig.
That would take away the fear to get going. In another thread I said, that it
may be a lot of work to migrate a lot of tomcat instances. But I guess most
ge-
>> From: Peter Kreuser
>> Sent: Thursday, August 11, 2022 4:00 PM
>> To: Tomcat Users List
>> Subject: Re: Simple SSL question
>>
>>
>> Jon and Chris,
>>
>>
>>> Am 11.08.2022 um 19:33 schrieb Christopher Schultz
>&
cooperation.
> -Original Message-
> From: Peter Kreuser
> Sent: Thursday, August 11, 2022 4:00 PM
> To: Tomcat Users List
> Subject: Re: Simple SSL question
>
>
> Jon and Chris,
>
>
> > Am 11.08.2022 um 19:33 schrieb Christopher Schultz
> :
I'm sure you'll sleep better at night after you've
> switched.
>
> -chris
>
>>> -Original Message-
>>> From: Christopher Schultz
>>> Sent: Thursday, August 11, 2022 11:29 AM
>>> To: users@tomcat.apache.org
>>> Subject: Re:
mple, you can configure both RSA and EC certificates for a single host.
That's just not possible with the one-attribute-to-rule-them-all configuration
where everything is on the element.
-chris
-Original Message-
From: Mark Thomas
Sent: Wednesday, August 10, 2022 2:43 PM
To: us
-Original Message-
> From: Christopher Schultz
> Sent: Thursday, August 11, 2022 11:29 AM
> To: users@tomcat.apache.org
> Subject: Re: Simple SSL question
>
> Jon,
>
> On 8/11/22 11:22, jonmcalexan...@wellsfargo.com.INVALID wrote:
> > Is there a "name"
a
single host. That's just not possible with the
one-attribute-to-rule-them-all configuration where everything is on the
element.
-chris
-Original Message-
From: Mark Thomas
Sent: Wednesday, August 10, 2022 2:43 PM
To: users@tomcat.apache.org
Subject: Re: Simple SSL question
On 1
rom: Mark Thomas
> Sent: Wednesday, August 10, 2022 2:43 PM
> To: users@tomcat.apache.org
> Subject: Re: Simple SSL question
>
> On 10/08/2022 19:22, jonmcalexan...@wellsfargo.com.INVALID wrote:
> > Ok, I'm asking a rather simple, stupid (in my opinion) question, but here
>
Thanks Mark!!!
> -Original Message-
> From: Mark Thomas
> Sent: Wednesday, August 10, 2022 2:43 PM
> To: users@tomcat.apache.org
> Subject: Re: Simple SSL question
>
> On 10/08/2022 19:22, jonmcalexan...@wellsfargo.com.INVALID wrote:
> > Ok, I'm askin
On 10/08/2022 19:22, jonmcalexan...@wellsfargo.com.INVALID wrote:
Ok, I'm asking a rather simple, stupid (in my opinion) question, but here goes:
What is the best practice form of connector for SSL. Is it the old-school coyote
connector or the connector with the section?
The old style isn'
Ok, I'm asking a rather simple, stupid (in my opinion) question, but here goes:
What is the best practice form of connector for SSL. Is it the old-school
coyote connector or the connector with the section?
Are the two interchangeable, or does the SSLHostConfig one rely on openssl and
won't wor
> From: Joan Balagueró Ventus Proxy [mailto:joan.balagu...@ventusproxy.com]
> Subject: SSL question
> When I shutdown Tomcat, I see this message in catalina.out (ssl debug
> enabled):
> main, called close()
> main, called closeInternal(true)
> main, SEND TLSv1 ALERT:
Hello,
I have an application that sends https requests with client authentication
from a servlet running on tomcat. Its working fine.
When I shutdown Tomcat, I see this message in catalina.out (ssl debug
enabled):
main, called close()
main, called closeInternal(true)
main, SEND TLSv1
The keystore won't accept my existing certificate if I put an alias of
'tomcat', and if I put no alias, it says it's not a valid X.509 certificate,
even though it's been loaded by IIS.
--- Peter Crowther <[EMAIL PROTECTED]> wrote:
> > From: Michael Bongiovi [mailto:[EMAIL PROTECTED]
> > But that'
> From: Michael Bongiovi [mailto:[EMAIL PROTECTED]
> But that's not working. I can get to the main site by going to
>
> https://www.mycompany.com
OK.
> but if I try to go to
>
> https://www.mycompany.com:8443
>
> I get a "page cannot be displayed" error despite the fact
> that I have the
> conne
But that's not working. I can get to the main site by going to
https://www.mycompany.com
but if I try to go to
https://www.mycompany.com:8443
I get a "page cannot be displayed" error despite the fact that I have the
connector code in server.xml uncommented so that it's available.
--- Peter
> From: Michael Bongiovi [mailto:[EMAIL PROTECTED]
> Unless I'm not understanding things correctly, setting up SSL
> on Tomcat would
> require getting another SSL certificate to be kept in the
> keystore for Tomcat,
> but I don't want to get another certificate since I already
> have one for main w
Michael Bongiovi wrote:
Unless I'm not understanding things correctly, setting up SSL on Tomcat would
require getting another SSL certificate to be kept in the keystore for Tomcat,
but I don't want to get another certificate since I already have one for main
web site itself. I assume that means
Unless I'm not understanding things correctly, setting up SSL on Tomcat would
require getting another SSL certificate to be kept in the keystore for Tomcat,
but I don't want to get another certificate since I already have one for main
web site itself. I assume that means having to go with the seco
> From: Michael Bongiovi [mailto:[EMAIL PROTECTED]
> I'm running Tomcat 5.5 as a servlet container under IIS so
> that I can run Jive
> forums on my web site. The forum is linked to from the main
> web page, which
> already has an SSL certificate. I'd like to be able to have
> the Jive login
> sc
I'm running Tomcat 5.5 as a servlet container under IIS so that I can run Jive
forums on my web site. The forum is linked to from the main web page, which
already has an SSL certificate. I'd like to be able to have the Jive login
screen passed through SSL, but I'm not sure how to do it. Any help
> Hello,
>
> I have SSL setup on tomcat port 8443, the ssl connection works for a
> while and then times out (not able to connection). However, the
> connection on port 80 is still active and I can connect with out any
> issues.
>
> Anyone seen this before. Any ideas.
>
> Thanks,
>
> Abi
>
Hello,
I have SSL setup on tomcat port 8443, the ssl connection works for a
while and then times out (not able to connection). However, the
connection on port 80 is still active and I can connect with out any
issues.
Anyone seen this before. Any ideas.
Thanks,
Abi
--
> From: Velurethu, Abi J [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat 4.1 SSL Question [Broadcast] [Broadcast]
>
> Sorry for the confusion. I meant I will set the non-ssl on
> port 80 and ssl on 8443.
If you are encountering the IE problem, you'll need to put SSL on 4
Users List
Subject: RE: Tomcat 4.1 SSL Question [Broadcast] [Broadcast]
> From: Velurethu, Abi J [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat 4.1 SSL Question [Broadcast]
>
> I will setup SSL on Tomcat 4.1 on port 80 and give it try.
Don't do that. The standard HTTPS port is
> From: Velurethu, Abi J [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat 4.1 SSL Question [Broadcast]
>
> I will setup SSL on Tomcat 4.1 on port 80 and give it try.
Don't do that. The standard HTTPS port is 443; enabling SSL on 80 will
create a real mess.
- Chuck
THIS
, September 14, 2007 9:39 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 4.1 SSL Question [Broadcast]
Since TC 4 does a redirect to the welcome-file, this also causes
problems
with IE when you use a non-default SSL port.
"Caldarale, Charles R" <[EMAIL PROTECTED]> wrote in mess
Since TC 4 does a redirect to the welcome-file, this also causes problems
with IE when you use a non-default SSL port.
"Caldarale, Charles R" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: T
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat 4.1 SSL Question
>
> I thought I'd seen that port was usually 8443. Or 443.
There's a problem with at least some versions of IE that insist on using
443 for HTTPS, regardless of what was used to r
I thought I'd seen that port was usually 8443. Or 443.
-Original Message-
From: Velurethu, Abi J [mailto:[EMAIL PROTECTED]
Sent: Friday, September 14, 2007 2:15 PM
To: users@tomcat.apache.org
Subject: Tomcat 4.1 SSL Question
> Hello,
>
> I have an issue with tomcat 4.1 SS
> Hello,
>
> I have an issue with tomcat 4.1 SSL setup. I am running multiple
> instances of Tomcat on one server, Tomcat 1, Tomcat 2, Tomcat 3...
>
> I am setting up SSL on one of the Tomcat instances...the non-ssl port
> is 8180 and it is working fine. The ssl port is 8444. I did all the
> c
diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: "Caldarale, Charles R" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Sunday, January 14, 2007 10:50 AM
Subject: RE: yet another SSL question
> From: [EMAIL PROTECTED] [mailto:[EMAI
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Subject: Re: yet another SSL question
>
> Is it possible to have multiple different Login pages in one webapp?
Yes; look at section 12.8 of the Servlet spec:
http://jcp.org/aboutJava/communityprocess/final/jsr154/index.html
U
first, thanks for your help.
But now I got the next problem:
Is it possible to have multiple different Login pages in one webapp?
Scenario:
- Two areas (DB,shop) in one webapp
- two groups of users having access to one of the areas.
- one member of both groups.
When I am logged in to the DB-se
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Subject: yet another SSL question
>
> What security-constraints do i need, and where do i have to put them?
The basis for Dhaval's suggestion is section 12 of the servlet spec,
obtainable here:
http://jcp.org/aboutJava/commu
Try this:
Secure servlet
/path/to/servlet/*
GET
POST
CONFIDENTIAL
Regards,
D
--- Jan Strauch <[EMAIL PROTECTED]> wrote:
> Hello world!
>
> My problem :
>
> I want some of my servlets to b
Hello world!
My problem :
I want some of my servlets to be accessible only when HTTPS is used:
https:/ succeeds
http:/ gives an error
The first step seems to work, but when i have logged in into the secure area,
load a page using https, delete the "s" and reload, the page is also loaded.
Thanks Filip,
It's now working as I thought it should. I did what you said as well as
manually configuring a worker and adding said worker to a virtual host for
port 443.
Oh and special thanks to Li.
David
On 8/4/06, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
set "redirectPort" on y
set "redirectPort" on your AJP(port 8009) connector to 443
http://tomcat.apache.org/tomcat-5.5-doc/config/ajp.html
using mod_jk, you will not use port 8080 and 8443, only 8009.
Filip
David Miller wrote:
I can't do that because the web server uses those ports.
Perhaps someone can just verify
I can't do that because the web server uses those ports.
Perhaps someone can just verify the following; will tomcat with mod_jk allow
me to access encrypted pages without seeing the port in the URL?
Example: we want to see this https://localhost/my-secured-webapp and NOT
this https://localhost:84
David Miller wrote:
> When I run my app using Tomcat only (without apache httpd) I specify the
> ports for secure and non-secure pages; http://localhost:8080/my-app or
> https://localhost:8443/my-app for example.
>
> I've installed mod_jk hoping that Apache httpd would handle
> the connection allo
When I run my app using Tomcat only (without apache httpd) I specify the
ports for secure and non-secure pages; http://localhost:8080/my-app or
https://localhost:8443/my-app for example.
I've installed mod_jk hoping that Apache httpd would handle
the connection allowing me to omit the port number
44 matches
Mail list logo
