WebLogic Proxy Plug-in On IIS 7 Server Not Handling both Transfer-Encoding and Content-Length Headers Together
(Doc ID 1394253.1)
Last updated on SEPTEMBER 29, 2020
Applies to:Oracle WebLogic Server - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
***Checked for relevance on 1-Nov-2013***
A WebLogic cluster has been configured with Microsoft IIS 7.0 running on Win2008 as a proxy server.
The application compresses a response to the client with gzip and adds the Content-Length leader to the response headers. When the response generated by the application is a large page, then WebLogic Server will also set the response header Transfer-Encoding=chunked.
When both the Content-Length and Transfer-Encoding headers reach the IIS web server configured with WebLogic proxy plugin 188.8.131.52 or higher, it will fail to write the response to the browser.
This issue is not seen on IIS 6 running on Win2003.
When accessing WebLogic Server directly from a browser (bypassing the proxy server), the application response is handled without error; when the IIS web server tries to write the response back to the client it fails.
If you run into this problem you may have made changes to the Request Filter code in the application.
If you have upgraded the IIS web server from version 6.0 to 7.0, you can see this problem.
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