On 14/09/2018 16:01, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 9/14/18 08:34, Mark Thomas wrote:
On 14/09/18 13:11, Tim K wrote:
Using latest Tomcat 9.0.11. I'm using the securePort attribute
for both the NioReceiver and StaticMembers but when cap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 9/14/18 08:34, Mark Thomas wrote:
> On 14/09/18 13:11, Tim K wrote:
>> Using latest Tomcat 9.0.11. I'm using the securePort attribute
>> for both the NioReceiver and StaticMembers but when capturing and
>> inspecting the traffic over the s
On 14/09/18 13:11, Tim K wrote:
> Using latest Tomcat 9.0.11. I'm using the securePort attribute for both
> the NioReceiver and StaticMembers but when capturing and inspecting the
> traffic over the secure ports with WireShark, I'm seeing all my session
> data in clear text, even my username as pa
Using latest Tomcat 9.0.11. I'm using the securePort attribute for both
the NioReceiver and StaticMembers but when capturing and inspecting the
traffic over the secure ports with WireShark, I'm seeing all my session
data in clear text, even my username as password (user principal)! I tried
removi