Chris,
On Thu, Nov 21, 2024 at 1:51 PM Christopher Schultz
wrote:
>
> Pawel,
>
> On 11/19/24 7:52 PM, Pawel Veselov wrote:
> > On Wed, Nov 20, 2024 at 1:26 AM Pawel Veselov
> > wrote:
> >>
> >> Hello.
> >>
> >> Upgrading Tomcat fro
On Wed, Nov 20, 2024 at 1:26 AM Pawel Veselov wrote:
>
> Hello.
>
> Upgrading Tomcat from 10.1.25 to 10.1.33 caused our sanity tests to
> fail as the "content-length" header field is no longer present in the
> HEAD responses.
>
> The application explicitly sets
Hello.
Upgrading Tomcat from 10.1.25 to 10.1.33 caused our sanity tests to
fail as the "content-length" header field is no longer present in the
HEAD responses.
The application explicitly sets the content-length header on HEAD requests.
The change is traced to this commit:
commit 8e786a8eda
Aut
Chris,
On Fri, Apr 19, 2024 at 4:40 AM Christopher Schultz
wrote:
>
> Pawel,
>
> On 4/18/24 20:21, Pawel Veselov wrote:
> >> On 18/04/2024 15:18, Stefan Ansing wrote:
> >>> Hi Rémy, Mark,
> >>> I just want to make sure that we’re understanding ea
On Thu, Apr 18, 2024 at 9:40 AM Adwait Kumar Singh wrote:
> > I'm not (yet) convinced distinguishing between those scenarios is always
> > going to be possible.
> I have a Tomcat patch which we use at work to do this, i.e always close the
> connection if HTTP parsing fails but not if it's a user
> On 18/04/2024 15:18, Stefan Ansing wrote:
> > Hi Rémy, Mark,
> > I just want to make sure that we’re understanding each other. I can see
> > that the connection needs to be closed in certain conditions to prevent
> > request smuggling attacks. I certainly don’t want to change that behaviour.
> >
Hello.
Ran into an interesting problem yesterday. After updating Tomcat to
9.0.69 to mitigate a disclosed CVE, some of our tests started failing.
Investigation uncovered that the HTTP client stopped accepting
"set-cookie" headers because of "expires" attribute values.
There was a change to the f
Hello.
I was wondering what exact value does Tomcat 9x use for NIO connector
socket timeouts?
I.e., when the following exception occurs:
org.apache.catalina.connector.ClientAbortException
java.net.SocketTimeoutException
at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.ja
Christopher, Stephan,
On Tue, Jul 5, 2022 at 11:18 PM Christopher Schultz
wrote:
>
> Stefan,
>
> On 7/2/22 09:45, Stefan Mayr wrote:
> > Hi,
> >
> > Am 01.07.2022 um 17:10 schrieb Christopher Schultz:
> >> Thomas,
> >>
> >> On 6/30/22 13:52, Thomas Meyer wrote:
> >>> Sadly currently Tomcat startu
Florian,
On Tue, May 3, 2022 at 3:12 PM Hagenauer, Florian
wrote:
> since Apple released Safari 15 (both iOS and macOS) I am running into a
> strange issue related to Apache Tomcat, Safari/WebKit and certain sequences
> of messages received via a WebSocket. When the browser receives messages in
Hello.
On Fri, Jul 2, 2021 at 1:04 AM Pawel Veselov wrote:
>
> Hello.
>
> We've been using Tomcat 9 OpenJDK(8) images for a while, but are now
> trying to switch to Corretto.
I sincerely apologize. I didn't realize that Tomcat images weren't maintained
by the To
Hello.
We've been using Tomcat 9 OpenJDK(8) images for a while, but are now
trying to switch to Corretto.
The problem we ran into is that tomcat-native is built with OpenSSL
1.0 libraries.
That makes it impossible to use Ed25519 certificates.
I don't think it's possible to rectify that at runtime
Hello!
Tomcat 9.0.x
I'd like to force connection closure on some endpoints.
I'm trying this on a simple JSP page.
If I call response.setHeader("Connection","close"), I see that the
response has "Connection: close, keep-alive".
I assume Tomcat inserts the keep-alive part. It looks like the browser
Hello.
I'm doing something where I need to generate a password for a tomcat user
that is authenticated using org.apache.catalina.realm.UserDatabaseRealm
with "sha" digest, the user database is
produced by org.apache.catalina.users.MemoryUserDatabaseFactory from an xml
file (standard conf/tomcat-us
Sorry for a rather rude intrusion.
On Thu, Feb 7, 2019 at 4:18 PM Christopher Schultz
wrote:
> Chunked encoding is like sending a bunch of small HTTP message-pieces
> (I have to be careful about my wording here, since "part" actually
> means something in multipart messages
May be just "chunks"?
Apologies for reviving a zombie.
On Sat, Feb 3, 2018 at 8:43 AM, Pawel Veselov wrote:
>>>> What is the problem with failures during pool initialization?
>>> ConnectionPool.init() attempts to borrow initialSize worth of
>>> connections. Imagine your database server
Chris,
On Fri, Feb 2, 2018 at 2:20 PM, Christopher Schultz
wrote:
> On 2/2/18 1:47 PM, Pawel Veselov wrote:
>>> On 2/1/18 6:08 PM, Pawel Veselov wrote:
>>>> On Thu, Feb 1, 2018 at 1:02 PM, Mark Thomas
>>>> wrote:
>>>>> On 01/02/18 20:57, Pawel
> On 2/1/18 6:08 PM, Pawel Veselov wrote:
>> On Thu, Feb 1, 2018 at 1:02 PM, Mark Thomas
>> wrote:
>>> On 01/02/18 20:57, Pawel Veselov wrote:
>>>> Hello.
>>>>
>>>> It looks like in tomcat 8 (looking at master's HEAD), the
&g
On Thu, Feb 1, 2018 at 1:02 PM, Mark Thomas wrote:
> On 01/02/18 20:57, Pawel Veselov wrote:
>> Hello.
>>
>> It looks like in tomcat 8 (looking at master's HEAD), the minIdle
>> support is broken. According to docs, minIdle supposed to do : "The
>> min
Hello.
It looks like in tomcat 8 (looking at master's HEAD), the minIdle
support is broken. According to docs, minIdle supposed to do : "The
minimum number of established connections that should be kept in the
pool at all times. The connection pool can shrink below this number if
validation querie
't get the actual name that
the bean is registered as (except for copying the code that
preRegister ends up calling). I ended up fishing the bean out by
querying it before unregistering it.
I hope things are, in fact, better in 9.
Thank you,
Pawel.
> 2018-01-24 10:48 GMT+09:00 Pawel Vese
Hello.
I'd like to get some JMX stats out of the JDBC connection pools. But
they don't seem to register
in JMX, even though they are based on ConnectionPoolMBean.
I do create the pools programmatically, by binding the factory into
the JNDI, the creation snippet is
copied below. When I search for
22 matches
Mail list logo
