from mobile (sorry for typos ;)
On Thu, Jan 23, 2025, 23:00 James Matlik wrote:
> It works!
>
> I've been able to test with a customer name of: ÀËÌÑàëíñøü / \ Ѐӿ 中さ 😀
> customer
> This covers
> - Latin-1 Supplement characters are 1 byte: ÀËÌÑàëíñøü
> - The / and \ slash characters are ASCII,
Christopher,
From: Christopher Schultz
Sent: Wednesday, January 22, 2025 11:19 AM
To: users@tomcat.apache.org
Subject: Re: Openssl Connector configuration for Dynamic Client Authorization
does not work.
Thomas, On 1/21/25 2: 08 PM, Timothy Resh wrote: > In the old configuration we
were able to
On 23/01/2025 14:34, Mark Thomas wrote:
All of that suggests that something detects an issue with this request
(or it just times out) which triggers the async error handling which
eventually leads to the async request being completed/dispatched.
In the case of the unit test, it was a client
It works!
I've been able to test with a customer name of: ÀËÌÑàëíñøü / \ Ѐӿ 中さ 😀
customer
This covers
- Latin-1 Supplement characters are 1 byte: ÀËÌÑàëíñøü
- The / and \ slash characters are ASCII, but are encoded due to special
meaning in a URL
- Cyrillic characters are 2 bytes: Ѐӿ
- Chinese
On 23/01/2025 14:42, anand raj wrote:
Hi all,
In Tomcat 10 there is --add-opens added default and does this mean Tomcat
required to access these.
Yes.
Also document information on what all are
accessed which requires these will be helpful.
Generally to implement the memory leak detection
Hi all,
In Tomcat 10 there is --add-opens added default and does this mean Tomcat
required to access these .Also document information on what all are
accessed which requires these will be helpful.
Thanks,
ANANDARAJ N
On 17/01/2025 10:05, Michael wrote:
I have two applications, A and B, running in Tomcat 10.1.28 on RHEL
8.10 with Java 21 (OpenJDK Runtime Environment Red_Hat-21.0.5.0.10-1).
Application uses an AsyncContext and SSE to send messages back to an
application running in a Chrome browser. Sometimes I
On 20/01/2025 20:44, Michael wrote:
On Fri, Jan 17, 2025 at 7:45 PM Michael wrote:
On Fri, Jan 17, 2025 at 3:51 PM Chuck Caldarale wrote:
In various logs from nightly(?) Tomcat test runs, I've been able to
find a similar problem. See this, for instance:
https://nightlies.apache.org/tomcat/
James,
I've added attributes (encodedReverseSolidusHandling and
encodedSolidusHandling) to the Context to provide control of how the
RequestDispatcher paths are processed.
Snapshots built after 12.00 UTC today should include the new attributes.
As I type, Tomcat 12 is available, Tomcat 11 is
