Can I point certificateRevocationListFile= to an empty file so it always
reverts to OCSP?
From: Mark Thomas
Sent: Friday, June 21, 2019 9:10 AM
To: users@tomcat.apache.org
Subject: Re: OCSP Connector on Tomcat 8.5 not working
On 21/06/2019 16:46, Michael Magnu
On 21/06/2019 16:46, Michael Magnuson wrote:
>
>
> Thanks. Is that setup using a CRL instead of OCSP?
It will work with either/both. I had a local OCSP responder running with
OpenSSL so I could monitor the requests and responses. OCSP was working
correctly. It rejected a cert that had been inva
On 21/06/2019 13:48, Leonid Rozenblyum wrote:
> Thank you!
I've looked and the behaviour in 8.0.30 appears to be the same. The
changes I was thinking of were a) much further back and b) unlikely to
impact distributable.
Mark
>
> On Fri, Jun 21, 2019 at 3:29 PM Mark Thomas wrote:
>
>> On 21/0
Thanks. Is that setup using a CRL instead of OCSP?
From: Mark Thomas
Sent: Friday, June 21, 2019 8:44 AM
To: users@tomcat.apache.org
Subject: Re: OCSP Connector on Tomcat 8.5 not working
On 21/06/2019 16:31, Michael Magnuson wrote:
> Hmm. It's still not worki
On 21/06/2019 16:31, Michael Magnuson wrote:
> Hmm. It's still not working at all for me. Can you post your SSL connector
> configuration?
Mark
>
>
>
>
> From: Mark Thomas
> Sent: Thursday, June 20, 2019 11:36 AM
> To: users@tomcat.apache.
Hmm. It's still not working at all for me. Can you post your SSL connector
configuration?
From: Mark Thomas
Sent: Thursday, June 20, 2019 11:36 AM
To: users@tomcat.apache.org
Subject: Re: OCSP Connector on Tomcat 8.5 not working
On 20/06/2019 18:50, Mark Tho
Am 2019-06-21 um 14:33 schrieb Mark Thomas:
On 21/06/2019 13:13, Osipov, Michael wrote:
Folks,
we're migrating off old hosts to new ones, but remain at 8.5.x (.34 to
.42 at the moment) and Java 8. Surprisingly, an empty Tomcat wih just
manager installed takes way too long too start. More pre
Thank you!
On Fri, Jun 21, 2019 at 3:29 PM Mark Thomas wrote:
> On 21/06/2019 12:39, Leonid Rozenblyum wrote:
> > Hi Mark!
> > Thanks for the explanation.
> >
> > So now it's mandatory for us to mark every web application
>
> > (and also ensure no dependencies in classpath are actual web fragme
On 21/06/2019 13:13, Osipov, Michael wrote:
> Folks,
>
> we're migrating off old hosts to new ones, but remain at 8.5.x (.34 to
> .42 at the moment) and Java 8. Surprisingly, an empty Tomcat wih just
> manager installed takes way too long too start. More precisely, the
> Tomcat is fast, deploying
On 21/06/2019 12:39, Leonid Rozenblyum wrote:
> Hi Mark!
> Thanks for the explanation.
>
> So now it's mandatory for us to mark every web application
> (and also ensure no dependencies in classpath are actual web fragments
> without distributable accidentally)
>
> About our upgrade:
> We've upgr
Folks,
we're migrating off old hosts to new ones, but remain at 8.5.x (.34 to
.42 at the moment) and Java 8. Surprisingly, an empty Tomcat wih just
manager installed takes way too long too start. More precisely, the
Tomcat is fast, deploying manager app is horribly slow:
2019-06-21T13:50:35
Hi Mark!
Thanks for the explanation.
So now it's mandatory for us to mark every web application
(and also ensure no dependencies in classpath are actual web fragments
without distributable accidentally)
About our upgrade:
We've upgraded Tomcat
Tomcat 8.0.30 -> Tomcat 9.0.16
(we are planning also
On 21/06/2019 11:04, Tommy Pham wrote:
> Thank you for the clarification and the heads up. I greatly appreciate it.
> I've been thinking about different methods of approach and I think this is
> better than servletPath + pathInfo:
>
> return getServletContext() == null ? null : getServl
Hi Mark,
On Thu, Jun 20, 2019 at 11:57 PM Mark Thomas wrote:
> On 21/06/2019 03:21, Tommy Pham wrote:
> >
> >
> > After some further research, it appears the issue I'm encountering is
> known
> > since 2007 by IBM at least:
> >
> > https://www-01.ibm.com/support/docview.wss?uid=swg21259282
> >
On 21/06/2019 09:54, Leonid Rozenblyum wrote:
> Hello. After recent Tomcat upgrade from 8.0 to 9.0 DeltaManager stopped
> initializing.
> StandardManager is used instead in cluster environment.
Could you be more specific about version numbers please.
> our global conf/web.xml contains as before.
Hello. After recent Tomcat upgrade from 8.0 to 9.0 DeltaManager stopped
initializing.
StandardManager is used instead in cluster environment.
our global conf/web.xml contains as before.
I found a possible workaround: to copy the tag to the
web.xml in the web applications itself.
However should
16 matches
Mail list logo
