On 29/03/2020 18:02, James H. H. Lampert wrote:
> Question:
>
> In order to serve a Content-Security-Policy header, we have installed a
> filter in the context-level web.xml, that calls classes we've added to
> our webapp.
>
> Is there a way to make new classes available globally, so they can be
> -Original Message-
> From: André Warnier (tomcat/perl)
> Sent: Saturday, March 28, 2020 5:35 PM
> To: users@tomcat.apache.org
> Subject: Re: Does Tomcat/Java get around the problem of 64K maximum
> client source ports?
>
> On 27.03.2020 21:39, Eric Robinson wrote:
> > FYI, I don't have 1
Question:
In order to serve a Content-Security-Policy header, we have installed a
filter in the context-level web.xml, that calls classes we've added to
our webapp.
Is there a way to make new classes available globally, so they can be
used by a filter in the global conf/web.xml? Someplace we
On 29/03/2020 15:58, Manuel Dominguez Sarmiento wrote:
>
>> Do the streams with errors all share the same connection ID? I suspect
>> an error on one stream is triggering the closure of the connection and
>> what you are seeing is the fallout of closing the connection.
> That makes sense and is ki
Do the streams with errors all share the same connection ID? I suspect
an error on one stream is triggering the closure of the connection and
what you are seeing is the fallout of closing the connection.
That makes sense and is kind of what we're suspecting. How can we check
the connection/stre
Thanks for the inputs, Mark.
Thanks,
Amit
> On Mar 29, 2020, at 5:06 PM, Mark Thomas wrote:
>
> On 29/03/2020 08:11, Amit Pande wrote:
>> Hello all,
>>
>> I was exploring Tomcat configuration which doesn't accept requests until the
>> web application is deployed.
>>
>>
>> "bindOnInit" conn
On 28/03/2020 14:00, Manuel Dominguez Sarmiento wrote:
> Hi Mark, we're now on the latest 9.0.33 release and we still see this
> issue intermittently in our logs. Only on HTTP/2 secure requests.
>
> Please see the attached access logs (these represent all the cases for
> one whole day in one singl
On 29/03/2020 08:11, Amit Pande wrote:
> Hello all,
>
> I was exploring Tomcat configuration which doesn't accept requests until the
> web application is deployed.
>
>
> "bindOnInit" connector attributes when set to false, makes socket bind when
> the connector starts and not when the connecto
Hello all,
I was exploring Tomcat configuration which doesn't accept requests until the
web application is deployed.
"bindOnInit" connector attributes when set to false, makes socket bind when the
connector starts and not when the connector is initialized.
Wanted to know, why the default valu
