What's the point of " ipv6v6only" attribute. The doc says :
"If listening on an IPv6 address on a dual stack system, should the connector
only listen on the IPv6 address? If not specified the default is false and the
connector will listen on the IPv6 address and the equivalent IPv4 address if
pr
On 11.03.2020 09:30, Piyush Kumar Nayak wrote:
What's the point of " ipv6v6only" attribute. The doc says :
"If listening on an IPv6 address on a dual stack system, should the connector only
listen on the IPv6 address? If not specified the default is false and the connector will
listen on the IP
On 10.03.2020 15:44, Martin Grigorov wrote:
On Tue, Mar 10, 2020 at 3:56 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 3/10/20 04:43, Martin Grigorov wrote:
We can define custom address like "loopback" for which Tomca
Tomcat 9
NetBeans 11.3
Windows 10
The JspWriter.autoFlush setting seems to be ignored. I confired that
isAutoFlush() is true (and it is) but my output (using JspWriter.print()) is
truncated. If I explicitly put flush() in my output loop, I get all the
data. Any direction would be appreciat
Hi All,
Due to the recent issues with Chrome 80, we have had to make some changes
for our context.xml to have SameSite attribute setup for CookieProcessor
What we've noticed is that even though CookieProcessorBase captures and
assigns the correct value (e.g. "None" or "Lax"), the Network tab of
b
Just to confirm, we know that Chrome will block JSESSIONID it if sent over
unsecure connection and with SameSite=None. But we saw the
previously mentioned issue in Firefox.
Thanks,
On Wed, 11 Mar 2020 at 15:33, M. Manna wrote:
> Hi All,
>
> Due to the recent issues with Chrome 80, we have had t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ed,
On 3/11/20 11:14, e...@wolfecomputerservices.com wrote:
> Tomcat 9
>
> NetBeans 11.3
>
> Windows 10
>
>
>
> The JspWriter.autoFlush setting seems to be ignored. I confired
> that isAutoFlush() is true (and it is) but my output (using
> JspWrite
Hi All,
I am using ISAPI redirector to connect IIS to Tomcat via AJP connector.
Recently I have replaced the Tomcat 9.0.22 with the new version 9.0.31.
I have set the new required attributes of the AJP connector in the new
9.0.31 version, and it is working fine when using http.
However, it return
Set this on AJP Connector in tomcat server.xml
allowedRequestAttributesPattern="CERT_(ISSUER|SUBJECT|COOKIE|FLAGS|SERIALNUMBER)|HTTPS_(SERVER_(SUBJECT|ISSUER)|(SECRETKEYSIZE|KEYSIZE))"
All on one line.
I can see tomcat fixing this in 9.0.32 which isn't yet released.
Thanks,
P.
-Original Mes
Hi KC
I hit that also. Turns out if I added this:
allowedRequestAttributesPattern=".*"
Then I got past the 403. I think this is supposed to be fixed in the next
release of tomcat.
Give it a shot.
Toby
-Original Message-
From: KC Mok
Sent: Wednesday, March 11, 2020 1
thank you very much, it is working now!
On Thu, Mar 12, 2020, 11:50 Mills, Robert - CTR [ASM Research]
wrote:
> Hi KC
>
> I hit that also. Turns out if I added this:
>
>allowedRequestAttributesPattern=".*"
>
> Then I got past the 403. I think this is supposed to be fixed in the
Btw, I tried my luck on Tomcat 7.0.100 before when 9.0.31 not work, also
hit the same problem, just fyi.
thanks again for helping me out!
On Thu, Mar 12, 2020, 11:55 KC Mok wrote:
> thank you very much, it is working now!
>
> On Thu, Mar 12, 2020, 11:50 Mills, Robert - CTR [ASM Research]
> wro
12 matches
Mail list logo
