Weblogic Server Sends Incorrect Response In Case Of A Non Standard HTTP Status Code
Last updated on JANUARY 14, 2018
Applies to:Oracle WebLogic Server - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
If an application sets a non standard HTTP status code e.g 901, 801, 700 etc, weblogic server sends entire body in the HTTP response status message. This causes any proxy client (OHS, Apache plugin etc ) to have a parsing failure which inturn result in the weblogic server being removed from the dynamic server list. This will cause the requests to be sent to other WLS managed server,
This behavior will cause session loss if session replication is not enabled. Additionally it will also cause performance overhead and incorrect session jumping across managed servers.
The following error message can be seen in the OHS logs ( OHS is used as proxy server)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms