Re: Connection Closure due to Fatal Stream with HTTP2

2020-06-13 Thread Michael Osipov
Am 2020-06-13 um 08:42 schrieb Chirag Dewan: Hi, We are observing that under high load, my clients start receiving a GoAway frame with error: *Connection[{id}], Stream[{id}] an error occurred during processing that was fatal to the connection.* Background : We have implemented our clients to

Tomcat rfc6265 Cookie Dates

2020-06-13 Thread S V Pavankumar
Hi, I am checking the RFC6265 as we wanted to switch to the RFC6265 Cookie processor. One thing I have noticed is around, the way cookie expires date is written to the response. As per the RFC the date should follow RFC1123 date format https://tools.ietf.org/html/rfc6265#section-4.1.1

Connection Closure due to Fatal Stream with HTTP2

2020-06-13 Thread Chirag Dewan
Hi, We are observing that under high load, my clients start receiving a GoAway frame with error: *Connection[{id}], Stream[{id}] an error occurred during processing that was fatal to the connection.* Background : We have implemented our clients to close connections after every 500-1000 requests