That's unfortunate. I haven't hit the issue in 9.0.102 but who knows -
it just might be even rarer...
On 3/11/25 11:41 AM, Ahmed Ashour wrote:
The issue still persists with 11.0.5.
Thanks,Ahmed
On Friday, March 7, 2025 at 11:20:18 AM GMT+1, Boris Petrov
wrote:
I
I've been doing that for the past few hours. For now all looks good.
I'll write here if I still see the problem - so hopefully you don't hear
from me today! :D
Thanks again!
Regards,
Boris
On 3/7/25 12:14 PM, Mark Thomas wrote:
On 07/03/2025 09:00, Boris Petrov wrote:
Hi Mar
As always, thanks for the hard work on Tomcat!
Regards,
Boris
On 1/20/25 10:31 AM, Mark Thomas wrote:
On 17/01/2025 15:31, Boris Petrov wrote:
Hi Mark,
I'm not sure what you mean that the error is being reported
client-side. It is, yes, but the backend itself returns status 500 -
so I gu
see what I can do about the client-side logging but that might
prove difficult...
Regards,
Boris
On 1/14/25 3:02 PM, Mark Thomas wrote:
On 16/12/2024 10:44, Mark Thomas wrote:
On 16/12/2024 10:28, Boris Petrov wrote:
Hi Mark,
Thanks for the response and sorry for the delayed answer.
I don&#x
ething out.
Regards,
Boris
On 12/11/24 10:17 AM, Mark Thomas wrote:
On 10/12/2024 08:28, Boris Petrov wrote:
I've been trying all versions of Tomcat since 9.0.93 (including the
newly released 9.0.98) and all of them have the same issue. I find it
extremely strange that no-one else hits th
give me builds to test with and I
send you back the results.
Regards, Boris
On 2024/10/09 16:42:08 Mark Thomas wrote:
> On 09/10/2024 03:33, Boris Petrov wrote:
> > I also have been experiencing the same issue (with Tomcat 9). 9.0.93
> > works fine. 9.0.94 is unusable. 9.0.95
I also have been experiencing the same issue (with Tomcat 9). 9.0.93
works fine. 9.0.94 is unusable. 9.0.95 and now 9.0.96 almost work but
sometimes I get the same behavior as with 9.0.94. I see it in my
integration tests - there are some sporadic failures here and there when
I upgrade from 9.0
On 3/23/21 6:25 PM, Mark Thomas wrote:
On 23/03/2021 16:09, Boris Petrov wrote:
Hi all,
I'm trying to figure out why Tomcat 9.0.44 seems to accept this URL:
https://some-domain.com/[foo: "bar@asd/qwe%25rty'zzzqqq{rrr|ttt]
Even when I haven't specified any "rel
Hi all,
I'm trying to figure out why Tomcat 9.0.44 seems to accept this URL:
https://some-domain.com/[foo: "bar@asd/qwe%25rty'zzzqqq{rrr|ttt]
Even when I haven't specified any "relaxedPathChars" (or when I
explicitly set it to an empty string). Note all the special characters
in it, including
ult, we've configured
Gradle to put such a timestamp. Thanks for the support!
Is the fix for issue 1 going to be in 9.0.25?
Thanks again,
Boris
On 9/12/19 6:21 PM, Mark Thomas wrote:
> On September 12, 2019 2:19:30 PM UTC, Boris Petrov
> wrote:
>> Hi,
>>
>> I ha
about the rest).
Why is Tomcat not changing the ETag header? This breaks for clients
which have already loaded it and don't get the new version because 304
is returned.
Thanks in advance,
Boris Petrov
-
To unsubscribe, e-m
doesn't
find and load the Listeners and Servlets. Where are we erring?
Another problem that I see with this code is our "manual" adding of a
mime mapping. Is there a "smarter" way to do that with Tomcat's
defaults? We saw Tomcat.DEFAULT_MIME_MAPPINGS but it is private...
Th
web.xml
and none of the other things a "webapp" provides. However, after
spending some time reading the code and Googling, I'm reaching the
conclusion that one cannot use "addContext" and have Tomcat use the
annotated classes. Am I right? Why is that, if so? And what
13 matches
Mail list logo
