The issue occurred again in Tomcat v10.1.40 but is fixed again in Tomcat
v10.1.41
On Thu, Apr 3, 2025 at 7:52 PM Mark Thomas wrote:
> On 03/04/2025 05:34, Tim N wrote:
> > That should have been
> >> Looks like this last worked Tomcat v10.1.20 and first failed v10.1.23
> >
> > ...and now looks li
and PARSE ERROR.
Are these errors being recorded by the client or the server?
The application is running on 6 VM's and each VM had 12 CPU and 36 GB RAM
Any suggestions to avoid these failures.
PARSE ERROR ought to be easy to track down and isn't really in-scope for
a Tomcat ma
Hell all,
The application hosted on tomcat9 exposes soap api which is consumed by SAP.
On a daily basis we are getting 200 thousands transactions and out of that
we could see around 1000 to 2000 failed transactions due to CONNECTION
REFUSED, CONNECTION CLOSED and PARSE ERROR.
The application is
On 03/04/2025 05:34, Tim N wrote:
That should have been
Looks like this last worked Tomcat v10.1.20 and first failed v10.1.23
...and now looks like this was first fixed again in v10.1.39
Any ideas why?
It suggests that the JasperInitializer was not trigger on start. If not
a packaging issu
That should have been
> Looks like this last worked Tomcat v10.1.20 and first failed v10.1.23
...and now looks like this was first fixed again in v10.1.39
Any ideas why?
On Sat, Feb 8, 2025 at 6:36 AM Tim N wrote:
> Looks like this last worked Tomcat v10.1.20 and first failed v19.1.23
>
> On F
>
>
>
> jsp
> *.jsp
> *.jspx
> *.vpp
> *.vsp
>
Rick Noel
Systems Programmer | Westwood One
rn...@westwoodone.com
-Original Message-
From: Rémy Maucherat
Sent: Friday, March 28, 2025 10:56 AM
To: Tomcat Users List
On Fri, Mar 28, 2025 at 3:28 PM Rick Noel wrote:
>
> We recently went from an error free tomcat 10 to the latest tomcat 11.0.5
> And now we get a muiti-part configuration error happening.
>
> The exact error message is this..
>
> org.apache.catalina.core.Applica
We recently went from an error free tomcat 10 to the latest tomcat 11.0.5
And now we get a muiti-part configuration error happening.
The exact error message is this..
org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for
servlet [jsp] threw exception
Hi Team,
FYI - The issue with 'Shutting down tomcat service throws system error 1067'
has been resolved in latest builds.
We started to see the issue since Tomcat version 9.0.90. Starting from 9.0.99
it looks like the issue disappeared / was fixed.
We do not have the issue in 9.0.1
'true' and then try to
detect within your app, if the client provided a valid certificate and
redirect them to an error page if that is not the case.
Source: https://stackoverflow.com/a/46488689/1180010
+1
If the TLS handshake fails (because the certs are unacceptable to one
party
n your app, if the client provided a valid certificate and
redirect them to an error page if that is not the case.
Source: https://stackoverflow.com/a/46488689/1180010
Sebastian
On 06.02.2025 18:59, Peter Rader wrote:
Hi,
I have a website that use mutual authentication for over 100 perso
Looks like this last worked Tomcat v10.1.20 and first failed v19.1.23
On Fri, Feb 7, 2025 at 3:22 PM Tim N wrote:
> I was launching my application successfully with Tomcat 10.1.16 using a
> JAR with all dependencies in a single JAR via "maven-assembly-plugin".
>
> Since upgrading to Tomcat 10.1.
I was launching my application successfully with Tomcat 10.1.16 using a JAR
with all dependencies in a single JAR via "maven-assembly-plugin".
Since upgrading to Tomcat 10.1.34, one of my applications is now throwing
java.lang.NullPointerException: Cannot invoke
"org.apache.jasper.compiler.TldCac
to have a custom website instead of the browser's
built-in error-page?
Kind regards
Peter Rader
--
Fachinformatiker AE / IT Software Developer
Peter Rader
Wilsnacker Strasse 17
10559 Berlin - GERMANY
Tel: 0049 (0)30 / 6 29 33 29 6
Fax: 0049 (0)30 / 6 29 33 29 6
Handy: 0049 (0)176 / 87 521 576
Hi Chris,
> Are there no logs or anything like that?
Our service stops quickly.
Nothing in logs though we redirect all tomcat logs into logs of our application.
> When Java encounters an error, it usually produces an hs_pid file which may
> be in an unusual location given the unusua
JVM dump file produced when the process terminated unexpectedly?
No
Can you post your connector configuration(s) - masking out any sensitive
information (eg, passwords)?
Interestingly, System Error 1067 is "The process terminated
unexpectedly" though you are intentionally s
al] Re: Shutting Down Tomcat (9.0.97) Service Throws System
Error 1067
[You don't often get email from n82...@gmail.com. Learn why this is important
at https://aka.ms/LearnAboutSenderIdentification ]
WARNING: This message was sent by someone outside Securitas. Please do not
reply, click
ies we are upgrading Tomcat to version 9.0.97.
> 3. The upgraded service works fine except when shutting down/stopping it.
> When we stop the service via either console or Services app, we get system
> error 1067 (please check the Appendix A).
> 4. Event Viewer does not contain too man
/stopping it. When
we stop the service via either console or Services app, we get system error
1067 (please check the Appendix A).
4. Event Viewer does not contain too many details about the issue (please check
the Appendix B).
5. Nothing in logs though we redirect Tomcat logs to logs of our
> On Oct 14, 2024, at 11:15, Kenaw, Seretseab
> wrote:
>
> We have an application hosted on Azure VM that runs on a Tomcat server and
> has a backend of Azure SQL database . There is a job that purges old data
> from the backend database and keeps failing after it runs for a few hours
> bec
i 14. lokakuuta 2024 19.16
To: users@tomcat.apache.org
Subject: Connection reset by peer: socket write error
[Et saa yleensä sähköpostia seretseab.ke...@ecolab.com.invalid. Lisätietoja
siitä, miksi tämä on tärkeää, on osoitteessa
https://aka.ms/LearnAboutSenderIdentification ]
Hello,
We have
Hello,
We have an application hosted on Azure VM that runs on a Tomcat server and has
a backend of Azure SQL database . There is a job that purges old data from the
backend database and keeps failing after it runs for a few hours because the
connection to database is getting closed for some rea
Ok 👍 sorry about that, I thought it would help him. It was for free advice, not
selling any service.
SD
From: Christopher Schultz
Sent: Friday, September 27, 2024 8:36:36 PM
To: users@tomcat.apache.org
Subject: Re: tomcat startup error, IBM DB2 related
don't post service advertisements to this list.
-chris
-Original Message-
From: Michael Lau
Sent: 24 September 2024 13:28
To: users@tomcat.apache.org
Cc: reggie.v.gokot...@accenture.com; neil.james.perdi...@accenture.com
Subject: tomcat startup error, IBM DB2 related (database)
.james.perdi...@accenture.com
Subject: tomcat startup error, IBM DB2 related (database)
Good afternoon,
we've been having trouble trying to start-up our server for a while, tried
restarting again and again and error still persists we can't run our website.
It's been ok for the past few w
On 24/09/2024 08:58, Michael Lau wrote:
here's a clip of the error from the cmd window of my friend:
0-Sep-2024 13:51:51.584 INFO [Timer-0]
org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading
Illegal access: this web application instance has been stopped al
Good afternoon,
we've been having trouble trying to start-up our server for a while, tried
restarting again and again and error still persists we can't run our
website. It's been ok for the past few weeks it's just we failed to shut
down the server properly and may have m
The issue I was having with migrating from Tomcat 9 to Tomcat 10.1 was the
packet size. Thanks for answering my question.
Thanks,
Lance
-Original Message-
From: Mark Thomas
Sent: Thursday, September 19, 2024 2:52 PM
To: users@tomcat.apache.org
Subject: Re: Error migrating to Tomcat
hould
have been identical to our previous version. A re-sync of the packet
size configuration got everything working perfectly again.
-chris
-Original Message-
From: Mark Thomas
Sent: Friday, September 20, 2024 1:23 AM
To: users@tomcat.apache.org
Subject: Re: Error migrating to Tomcat 10
hen worked. I
believe that if you call resp.sendRedirect you may not be able to do anything
else with the resp. This is just a guess.
Lance
-Original Message-
From: Mark Thomas
Sent: Friday, September 20, 2024 1:23 AM
To: users@tomcat.apache.org
Subject: Re: Error migrating to Tomcat 1
*.navigation.
Now I am using Java 17 and Tomcat 10.1 with version 5.0 of the web-app specs.
Is the above allowed with a URL redirection?
Yes.
I think the *.xyz might be the issue with HttpServletResponse sendRedirect .
> > Thoughts?
Unlikely related given the error you are seeing.
@tomcat.apache.org
Subject: Re: Error migrating to Tomcat 10.1
On 19/09/2024 20:19, Campbell, Lance wrote:
> I am using the latest Tomcat 10.1
>
> Java 17
>
> Apache Web server communicates with an application server running tomcat.
> The application name is webtools.
>
> I am
have a packetSize attribute? If yes,
you need to copy that across to 10.1
You can also check your work configuration on httpd for max_packet_size.
The two values have to agree.
Mark
I am getting this error in the tomcat app after sending a web request. It seems
like it is starting to load
I am using the latest Tomcat 10.1
Java 17
Apache Web server communicates with an application server running tomcat. The
application name is webtools.
I am migrating a working app from Tomcat 9 to Tomcat 10.1.
I am getting this error in the tomcat app after sending a web request. It seems
nt
> Gesendet: Donnerstag, 5. September 2024 04:36
> An: users@tomcat.apache.org
> Betreff: Re: How to resolve 403 forbidden error in Tomcat level
>
>
>
>
> On 9/3/24 11:22, Christopher Schultz wrote:
> > Jagadish,
> >
> > On 8/30/24 10:52, jagad
eing what you
are posting. Please post text-only.
-chris
On 8/29/24 11:01, jagadish sahu wrote:
> Hi Team and Christopher,
>
> We have attached a 403 error screenshot with full information.
> The error seems to be generated from Tomcat level.
>
posting. Please post text-only.
-chris
On 8/29/24 11:01, jagadish sahu wrote:
Hi Team and Christopher,
We have attached a 403 error screenshot with full information.
The error seems to be generated from Tomcat level.
We don't have any changes in the java code and our application is
working
:37 AM Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
>> Jadgish,
>>
>> This list does not accept image attachments. We are not seeing what you
>> are posting. Please post text-only.
>>
>> -chris
>>
>> On 8/29/24 11:01, jagadish sahu wro
Hi Tim
Thanks for the reply let me check the same with the app team.
Regards
Man Mohan
-Original Message-
From: Tim Funk
Sent: 03 September 2024 19:48
To: Tomcat Users List
Subject: Re: Tomcat 9.0.93 Patching | Error- A fatal error has been detected by
the Java Runtime Environment
"sigar-amd64-winnt.dll" is triggering the error. The details will be
in the core dump.
The vendor which supports "sigar-amd64-winnt.dll" will need to fix it.
Based on the release revisions, I suspect the DLL is using a reference
to a request or response object *after* the
Hi Mark
Thanks for the reply but same application is working fine with Tomcat 9.0.88.
Regards
Man Mohan
-Original Message-
From: Mark Thomas
Sent: 03 September 2024 18:29
To: Tomcat Users List
Subject: Re: Tomcat 9.0.93 Patching | Error- A fatal error has been detected by
the Java
9.0.90/93* and then we are getting below issue while starting the
tomcat after the patching and it is generating mdmp file after each
start and after that services got stopped.
*OS: Window *
*JAVA: 1.8.421*
*Tomcat : 9.0.90/93* (both having issue)
Error:
# A fatal error has been detected by
/93 (both having issue)
Error:
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x10014ed4, pid=7624,
tid=0x0ad0
#
# JRE version: Java(TM) SE Runtime Environment (8.0_421) (build 1.8.0_421-b09)
# Java VM: Java
Jadgish,
This list does not accept image attachments. We are not seeing what you
are posting. Please post text-only.
-chris
On 8/29/24 11:01, jagadish sahu wrote:
Hi Team and Christopher,
We have attached a 403 error screenshot with full information.
The error seems to be generated from
Hello Jagadish,
> Von: jagadish sahu
> Gesendet: Donnerstag, 29. August 2024 17:02
> An: Tomcat Users List ; Christopher Schultz
>
> Betreff: Re: How to resolve 403 forbidden error in Tomcat level
>
> Hi Team and Christopher,
>
> We have attached a 403 error scree
Hi Team and Christopher,
We have attached a 403 error screenshot with full information.
The error seems to be generated from Tomcat level.
We don't have any changes in the java code and our application is working
as expected in Tomcat 9.0.14.
After upgrading to latest version Tomcat,we
session, you can click on Ok to continue the session,
after clicking Ok we are getting a 403 error message (attached
screenshot for your reference).
Your screenshot has been stripped from the list. Is this an
application-generated 403 or one from Tomcat?
The correct functionality is it
session, after
clicking Ok we are getting a 403 error message (attached screenshot for
your reference).
The correct functionality is it should not get any error message, after
clicking waring message it should redirect to login page again, but in the
latest version of tomcat its not working, so we
http://www.catb.org/~esr/faqs/smart-questions.html
On 28/08/2024 17:02, jagadish sahu wrote:
Hi Team,
I am getting an error 403 forbidden error in my application. I want to fix
errors in Tomcat level.
Anything I need to change in tomcat level.
I am using tomcat 9.0.91.
Thank you
Jagadish
Hi Team,
I am getting an error 403 forbidden error in my application. I want to fix
errors in Tomcat level.
Anything I need to change in tomcat level.
I am using tomcat 9.0.91.
Thank you
Jagadish
Mark,
On 8/16/24 11:38, Mark Thomas wrote:
On 16/08/2024 16:16, Fernando wrote:
Hi all,
I need help with problem that I can't fix.
I am using Apache Tomee 8, but I know that Apache Tomee rest on Apache
Tomcat, in this case version 9.
My problem is when some user exit from application this forwa
On 16/08/2024 16:16, Fernando wrote:
Hi all,
I need help with problem that I can't fix.
I am using Apache Tomee 8, but I know that Apache Tomee rest on Apache
Tomcat, in this case version 9.
My problem is when some user exit from application this forward to login
page doing this:
HttpSession
Hi all,
I need help with problem that I can't fix.
I am using Apache Tomee 8, but I know that Apache Tomee rest on Apache
Tomcat, in this case version 9.
My problem is when some user exit from application this forward to login
page doing this:
HttpSession session = request.getSession();
sessi
Thank you Mark!
From: Mark Thomas
Sent: Monday, July 22, 2024 9:59 AM
To: users@tomcat.apache.org
Subject: Re: NoClassDef error
On 22/07/2024 15: 31, Mcalexander, Jon J. wrote: > Hello, > I have an
application team that is receiving the following exception after upgrading to
Tomcat 9.
sed on this message or any
information herein. If you have received this message in error, please advise
the sender immediately by reply e-mail and delete this message. Thank you for
your cooperation.
-
To unsubscribe, e-mail: use
action based on this message or any
information herein. If you have received this message in error, please advise
the sender immediately by reply e-mail and delete this message. Thank you for
your cooperation.
il -f /app/web/logs/RMA/RMA.log
2024-06-22 06:34:31,696{ INFO [http-bio-8443-exec-3] (RMAdao.java:5047) - after
preparing the statement
2024-06-22 06:34:31,697{ INFO [http-bio-8443-exec-3] (RMAdao.java:5050) -
application name is:RMA
2024-06-22 06:34:31,737{ERROR [http-bio-8443-exec-3] (RMAdao.
~]# tail -f /app/web/logs/RMA/RMA.log
>
> 2024-06-22 06:34:31,696{ INFO [http-bio-8443-exec-3] (RMAdao.java:5047) -
> after preparing the statement
>
> 2024-06-22 06:34:31,697{ INFO [http-bio-8443-exec-3] (RMAdao.java:5050) -
> application name is:RMA
>
> 2024-06-22 06:34:31,737
4-06-22 06:34:31,697{ INFO [http-bio-8443-exec-3] (RMAdao.java:5050) -
application name is:RMA
2024-06-22 06:34:31,737{ERROR [http-bio-8443-exec-3] (RMAdao.java:5116) - The
exception occurred is:ORA-00942: table or view does not exist
2024-06-22 06:34:31,738{ERROR [http-bio-8443-exec-3]
issue with JSP compilation. I'd suggest stopping
Tomcat, cleaning out the work directory and then starting Tomcat.
Mark
Last week I changed the user of the Tomcat services.
When I refresh teh page then every second time the page appears
correctly and the other 50% I get the error
No
Hello
we use Apache Tomcat/8.5.99.
Last week I changed the user of the Tomcat services.
When I refresh teh page then every second time the page appears correctly
and the other 50% I get the error
No I get intermittent error 404
The origin server did not find a current representation for the
Please don't respond to this email. I was able to figure out the issue. The
server hosting devexample.domain.com was using a canonicalized hostname.
This was throwing tomcat off when reading over the token and keytab file. I
only wish there was a better way for this error to pick up on that
application is hosted on Tomcat 9.0.54.
Domain: domain.com
Site: devexample.domain.com
URL hit: https://devexample.domain.com/webclient_devex/exclient.jsp
*I keep getting this when accessing the application on instance 5:*
HTTP Status 500 – Internal Server Error
Type Exception Report
Message
the Tomcat the
SAML2 Authentication, after the update to the Version 9.0.79 we are
seeing in the “stdout.log” File the following message:
13:26:17.576 [main] ERROR
org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider -
Error occurred while attempting to refresh metadata from
update to the Version 9.0.79 we are seeing in the
"stdout.log" File the following message:
13:26:17.576 [main] ERROR
org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider - Error
occurred while attempting to refresh metadata from
'E:\WEB-INF\idp-meta
Request/Response objects being
recycled without my non-container thread being aware of it or having to
block my container thread.
The concurrency requirements for asynchronous processing are set out in
section 2.3.3.4 of the Servlet specification.
Implementing Error handling is significantly
my non-container thread being aware of it or having to
block my container thread.
On Sat, Nov 25, 2023 at 5:42 AM Mark Thomas wrote:
> On 25/11/2023 05:30, Adwait Kumar Singh wrote:
>
> > Is there a way around this, to keep the async context open even on an
> error
> >
On 25/11/2023 05:30, Adwait Kumar Singh wrote:
Is there a way around this, to keep the async context open even on an error
and not close it till complete is invoked?
No. The spec requires the error handler to call complete() in onError()
and error handler doesn't, the container must.
hen I close it on the
async thread when its done.
However what I am observing is irrespective of if my not closing the
context, it's closed by default by Tomcat and the request/response objects
are recycled. Due to this during the error handling when I am trying to
read some heade
>On 07/11/2023 14:05, Tuukka Ilomäki wrote:
>> We have a very old application running on Tomcat 8.5.90. After upgrading
>> from JRE 8.0.252.09 from AdoptOpenJDK to 8u302b08 from Temurin (both pretty
>> old, I know, also newer JREs exhibit the same issue) we started having
>> NS_ERROR_NET_PARTIAL
On 07/11/2023 14:05, Tuukka Ilomäki wrote:
We have a very old application running on Tomcat 8.5.90. After upgrading from
JRE 8.0.252.09 from AdoptOpenJDK to 8u302b08 from Temurin (both pretty old, I
know, also newer JREs exhibit the same issue) we started having
NS_ERROR_NET_PARTIAL_TRANSFER i
We have a very old application running on Tomcat 8.5.90. After upgrading from
JRE 8.0.252.09 from AdoptOpenJDK to 8u302b08 from Temurin (both pretty old, I
know, also newer JREs exhibit the same issue) we started having
NS_ERROR_NET_PARTIAL_TRANSFER in FireFox and ERR_INCOMPLETE_CHUNKED_ENCODING
stener.
>> >
>> > In the onError of the ReadListener, I am catching a
>> SocketTimeoutException
>> > and trying to send back an error code 408. Here is the simplified
>> example
>> > of what I am trying to do,
>> >
>> > @Override
>>
; > I am using the async Servlet API and NIO, by setting a ReadListener.
> >
> > In the onError of the ReadListener, I am catching a
> SocketTimeoutException
> > and trying to send back an error code 408. Here is the simplified example
> > of what I am trying to do
On 30/10/2023 22:25, Adwait Kumar Singh wrote:
Hi,
I am using the async Servlet API and NIO, by setting a ReadListener.
In the onError of the ReadListener, I am catching a SocketTimeoutException
and trying to send back an error code 408. Here is the simplified example
of what I am trying to
FYI, I am doing the async processing on the Container thread itself, just
that I yield the thread back if I can't read without blocking.
Based on the code here
<https://github.com/apache/tomcat/blob/main/java/org/apache/coyote/AbstractProcessor.java#L121-L122>,
I see that the er
Hi,
I am using the async Servlet API and NIO, by setting a ReadListener.
In the onError of the ReadListener, I am catching a SocketTimeoutException
and trying to send back an error code 408. Here is the simplified example
of what I am trying to do,
@Override
> public void onError(Throwa
error, please advise
the sender immediately by reply e-mail and delete this message. Thank you for
your cooperation
> -Original Message-
> From: Mark Thomas
> Sent: Monday, October 16, 2023 5:21 PM
> To: users@tomcat.apache.org
> Subject: Re: error valve
>
>
On 16/10/2023 23:04, Mcalexander, Jon J. wrote:
Good afternoon all!
I have a question around the error valve. It mentions that if you want you can
supply custom error pages that need to be relative to $CATALINA_BASE. My
question is, just where should this go? Do you typically create an errors
Good afternoon all!
I have a question around the error valve. It mentions that if you want you can
supply custom error pages that need to be relative to $CATALINA_BASE. My
question is, just where should this go? Do you typically create an errors
directory under $CATALINA_BASE and put those
thanks mark,
Nithin P
On Tue, 03 Oct 2023 15:05:31 +0530 Mark Thomas wrote ---
On 03/10/2023 06:16, Nithin P wrote:
> Hi,
>
> I'm using Apache Ofbiz v18.12.06 While I'm trying to upload an image for
> vulnerability scanning it shows CVE-2020-1938. I have tried to update to
On 03/10/2023 06:16, Nithin P wrote:
Hi,
I'm using Apache Ofbiz v18.12.06 While I'm trying to upload an image for
vulnerability scanning it shows CVE-2020-1938. I have tried to update to the
latest version having the same issue, Does Anyone know where the tomcat conf
files are stored in the A
Hi,
I'm using Apache Ofbiz v18.12.06 While I'm trying to upload an image for
vulnerability scanning it shows CVE-2020-1938. I have tried to update to the
latest version having the same issue, Does Anyone know where the tomcat conf
files are stored in the Apache OFBiz application or how to di
"cosmetic imperfection" and maybe ask also the
burpsuite-team if this finding is justified.
I wish all a nice weekend!
Thomas
> -Ursprüngliche Nachricht-
> Von: Roberto Benedetti
> Gesendet: Samstag, 16. September 2023 11:46
> An: Tomcat Users List
> Betreff: R:
other
security options are left to Tomcat.
We had the same issue and that's how we passed the pen-test.
Roberto
-Messaggio originale-
Da: Peter Kreuser
Inviato: venerdì 15 settembre 2023 21:34
A: Tomcat Users List
Oggetto: Re: HSTS on 401 / error pages
CAUTION - This e
; -Ursprüngliche Nachricht-
>> Von: Christopher Schultz
>> Gesendet: Freitag, 15. September 2023 17:15
>> An: users@tomcat.apache.org
>> Betreff: Re: AW: HSTS on 401 / error pages
>>
>> Thomas,
>>
>>> On 9/14/23 10:03, Thomas Hoffmann
Hello Christ,
> -Ursprüngliche Nachricht-
> Von: Christopher Schultz
> Gesendet: Freitag, 15. September 2023 17:15
> An: users@tomcat.apache.org
> Betreff: Re: AW: HSTS on 401 / error pages
>
> Thomas,
>
> On 9/14/23 10:03, Thomas Hoffmann (Speed4Trade G
Thomas,
On 9/14/23 10:03, Thomas Hoffmann (Speed4Trade GmbH) wrote:
Hello Chris,
-Ursprüngliche Nachricht-
Von: Christopher Schultz
Gesendet: Donnerstag, 14. September 2023 15:26
An: users@tomcat.apache.org
Betreff: Re: HSTS on 401 / error pages
Thomas,
Please start a new thread
Hello Shawn,
> -Ursprüngliche Nachricht-
> Von: Shawn Heisey
> Gesendet: Freitag, 15. September 2023 03:56
> An: Tomcat Users List
> Betreff: Re: AW: HSTS on 401 / error pages
>
> On 9/14/23 08:03, Thomas Hoffmann (Speed4Trade GmbH) wrote:
> > Sorry, I thoug
On 9/14/23 08:03, Thomas Hoffmann (Speed4Trade GmbH) wrote:
Sorry, I thought removing all content and subject is sufficient. Maybe the
message-id header is used internally(?)
TL;DR: technical details about message threading. Not about Tomcat.
This is what happens when you reply to an existin
rade GmbH)
> :
>
> Hello Chris,
>
>> -Ursprüngliche Nachricht-
>> Von: Christopher Schultz
>> Gesendet: Donnerstag, 14. September 2023 15:26
>> An: users@tomcat.apache.org
>> Betreff: Re: HSTS on 401 / error pages
>>
>> Thomas,
>>
&
Hello Chris,
> -Ursprüngliche Nachricht-
> Von: Christopher Schultz
> Gesendet: Donnerstag, 14. September 2023 15:26
> An: users@tomcat.apache.org
> Betreff: Re: HSTS on 401 / error pages
>
> Thomas,
>
> Please start a new thread next time.
Sorry, I thoug
complains that HSTS header is missing on
401 responses.
I couldn’t find much information about whether HSTS makes sense for error pages.
It seems that Tomcat doesn’t send HSTS on 401 pages but burpsuite expects the
header.
Are there any pros and cons about sending HSTS on 401 response?
You should
sense for error pages.
It seems that Tomcat doesn’t send HSTS on 401 pages but burpsuite expects the
header.
Are there any pros and cons about sending HSTS on 401 response?
Thanks in advance!
Thomas
-
To unsubscribe, e-mail
Hi all.
Finally found out the issue.
And had nothing to do with tomcat.
There are two web applications under this particular instance of tomcat
Both of them contain an http client that issues https connections.
Application A sets explicitly the certificate store type to PKCS
Application B d
Ivano,
On 6/27/23 09:15, Ivano Luberti wrote:
We had another Linux server that should have been identical to the one
where the problem was occuring. Tested the same software on that without
the issue.
So we cloned the latter and replaced the former.
>
Now everything works as expected.
Hah
Hi Chris, thank you for your dedication.
We had another Linux server that should have been identical to the one
where the problem was occuring. Tested the same software on that without
the issue.
So we cloned the latter and replaced the former.
Now everything works as expected.
Before the r
Ivano,
On 6/8/23 06:10, Ivano Luberti wrote:
Hi, all I have the following problem.
[snip]
My guess is that looking at the code in this general area would be
helpful. If you are able to add debug logging in there to spoit-out some
of the crypto configuration being used, I'm sure it would hel
berti wrote:
My web application executes an SSL connection but fails with the
following exception
AxisFault: java.security.NoSuchAlgorithmException: Error
constructing implementation (algorithm: Default, provider: SunJSSE,
class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
That "
Ivano,
On 6/8/23 06:10, Ivano Luberti wrote:
My web application executes an SSL connection but fails with the
following exception
AxisFault: java.security.NoSuchAlgorithmException: Error constructing
implementation (algorithm: Default, provider: SunJSSE, class
1 - 100 of 1016 matches
Mail list logo
