Hi All,
Can someone please help on this ? It is in production and affecting many
customers. Upgrading tomcat is a big task.
Any pointers will be really appreciated.
Thanks
Naveen
On Wed, Jun 10, 2020 at 4:24 PM Naveen Kumar wrote:
> Hi Luis,
>
> Thanks for your suggestion.
> But I am wondering
Hi Chris,
Just attached the outputs logs and my server.xml including my ecdsa cert.
in keystoreand s_client outputs.txt file i have attached all the required
cert and keystore outputs.
What client are you using to attempt the handshake? i am using openssl
command line utility to test
What error(
Perhaps also compare your logging sensitivity between the servers.
Dream * Excel * Explore * Inspire
Jon McAlexander
Asst Vice President
Middleware Product Engineering
Enterprise CIO | Platform Services | Middleware | Infrastructure Solutions
8080 Cobblestone Rd | Urbandale, IA 50322
MAC: F4469
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alfred,
On 6/11/20 11:57, Alfred Bakia wrote:
> Hi Everyone,
>
> This is my very first mail to the users list since joining
> yesterday. Not an auspicious start. But I hope I will be able to
> contribute in future. I seek your help for a persistent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Madhan,
On 6/10/20 22:08, Madhan Raj wrote:
> Any insights please .
How did you create your certificate?
What are the details of your certificate and key? For example, which
curve are you using? How many key bits? What type of signature on the
cer
Hi Everyone,
This is my very first mail to the users list since joining yesterday. Not an
auspicious start. But I hope I will be able to contribute in future. I seek
your help for a persistent issue in one of our ColdFusion instances.
Description of issue:
ColdFusion 2018 is an application serv
On 11/06/2020 16:09, S Abirami wrote:
> Hi Mark,
>
> We don't have concern regarding the restart of tomcat for the changes in
> context.xml. As our web application is mainly used to launch only the
> standalone application.
> I have updated Cookieprocessor entry under the context tag in server.x
Hi Mark,
We don't have concern regarding the restart of tomcat for the changes in
context.xml. As our web application is mainly used to launch only the
standalone application.
I have updated Cookieprocessor entry under the context tag in server.xml
specific to the application context path and i
On June 11, 2020 2:32:51 PM UTC, S Abirami
wrote:
>Hi Mark,
>
>We are using Apache Tomcat 9.0.33.
>I am not seeing any exception regarding it.
That isn't what I asked. I asked for the log messages .
Fortunately, you have provided the information I was looking for below.
>In our application the
Hi Mark,
We are using Apache Tomcat 9.0.33.
I am not seeing any exception regarding it.
In our application the web-application will not be located under the
CATALINA_HOME/webapps location.
We placed in other location and mentioned the path in context tag with
attributes path and docBase in serv
On 11/06/2020 12:46, S Abirami wrote:
> Hi Mark,
>
> The below is the content of the context.xml
>
>
>
>
>
That looks OK.
What Tomcat version are you using?
What do the logs say when the application is deployed? That will tell
you where it is being deployed from which might suggest why tha
Hi Mark,
The below is the content of the context.xml
Regards,
Abirami.S
-Original Message-
From: Mark Thomas
Sent: Thursday, June 11, 2020 5:12 PM
To: users@tomcat.apache.org
Subject: Re: context.xml under META-INF was not working
On 11/06/2020 11:42, S Abirami wrote:
> Hi All,
>
On 11/06/2020 11:42, S Abirami wrote:
> Hi All,
>
> I want to configure SameSite attribute to the specific web-application.
> For that, I have updated the context.xml of specific web application located
> in /META-INF/context.xml
>
>
>
>
> It is not working. Only the changes in global context
Hi All,
I want to configure SameSite attribute to the specific web-application.
For that, I have updated the context.xml of specific web application located in
/META-INF/context.xml
It is not working. Only the changes in global context.xml is working. Please
guide to solve the issue.
Regard
Sorry for late reply. We have fixed the issue. Kubernetes ingress file was
causing multiple requests to be sent over and over again. Proxy timeout
along with read and send timeouts were not present in that file. We have
added them and now the process is working fine allowing it to complete with
onl
15 matches
Mail list logo