-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jared,
On 5/18/17 1:24 PM, Jared Walker wrote:
> Now, I know this is only a work around as the "spec" being used by
> this client is ancient. We are considering using the legacy parser
> as a stop-gap measure until we can update the external
On 18/05/2017 19:12, Caldarale, Charles R wrote:
From: jared.paul.wal...@gmail.com [mailto:jared.paul.wal...@gmail.com] On
Behalf Of Jared Walker
Subject: Tomcat 8.5.4 and LegacyCookieProcessor
We are migrating to the version of tomcat identified in the subject
Before exposing an almost
> From: jared.paul.wal...@gmail.com [mailto:jared.paul.wal...@gmail.com] On
> Behalf Of Jared Walker
> Subject: Tomcat 8.5.4 and LegacyCookieProcessor
> We are migrating to the version of tomcat identified in the subject
Before exposing an almost year-old version to the nasty rea
Hello,
We are migrating to the version of tomcat identified in the subject
and during our testing we ran into an issue with an external automated
client used to submit specialized requests to your web application.
It was failing to connect because it was submitting cookies with
version set to 0.
