Sporadic HTTPS Response Corruption on GlassFish 126.96.36.199 and 188.8.131.52
(Doc ID 1957918.1)
Last updated on MAY 07, 2020
Applies to:Oracle GlassFish Server - Version 2.1.1 and later
Information in this document applies to any platform.
Very sporadically some responses to requests over HTTPS return invalid content, potentially with stale data from another request. The problem is not seen with HTTP requests, only HTTPS and appears to be triggered when large volumes of data are being returned to a client and the client exits before all the data has been read. This is very infrequent and therefore potentially very difficult to detect. One way is to have a health-checking client that makes a request to a non-existent servlet or jsp over HTTPS. The response to this should return a HTTP 404 error page, but if a HTTP 200 or other data is returned then the problem has been encountered.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document