Chuck,
Unfortunately, the old cert is no longer available. Not sure what URL
the server would redirect to: 302 error whether I use http or https for
the request. I'm really stuck on this one. Worse, it's critical since
our payment server must send a response to us via https.
Any idea what else to try? I commented out the AJP connector since I'm
not fronting this with apache, just using tomcat as a server.
Thanks again.
Greg.
Caldarale, Charles R wrote:
From: Greg Brownell [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat ssl/https: error 302 when accessing
servlet with https
As for <auth-constraint>, users never had to authenticate
before accessing the servlet(s).
Yes, you're right - I just verified that lack of any <auth-constraint>,
as opposed to an <auth-constraint> with no roles, allows access to all.
Reading the original question more closely, the 302 is not an error -
it's just a redirect from the server supplying a different URL for the
browser to try. This happens, for example, if you attempt access via
HTTP, and the server redirects to HTTPS.
Since this timeout appeared only after you changed certificates, have
you tried going back to the prior one?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
