iPlanet Web Proxy Server 4.0 Forwards POST Request Headers Without POST Entity Body (Doc ID 1136458.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Sun Java System Web Proxy Server - Version: 4.0 and later   [Release: 4.0 and later ]
Sun Java System Web Server - Version: 7.0 and later    [Release: 7.0 and later]
Information in this document applies to any platform.

Symptoms

If the POST entity body of a POST request comes in a separate TCP packet, the proxy server in reverse mode forwards the POST request and headers to the origin server without sending the POST entity body.  This causes interoperability problems with the origin server, Oracle iPlanet Web Server 7.0.  From the origin server side, the problem results in the next request getting truncated. 

For example, if the next request is:
GET / HTTP/1.0

Oracle iPlanet Web Server 7.0 as the origin server would truncate the request into:
ET / HTTP/1.0

The Oracle iPlanet Web Server 7.0 resulting response code for this second request would be a "501 Not Implemented" HTTP response code:
HTTP/1.1 501 Not Implemented
Server: Sun-Java-System-Web-Server/7.0
Date: Fri, 19 Mar 2010 01:39:31 GMT
Content-length: 148
Content-type: text/html
Connection: close

<HTML><HEAD><TITLE>Not Implemented</TITLE></HEAD>
<BODY><H1>Not Implemented</H1>
This server does not implement the requested method.
</BODY></HTML>Connection to localhost closed by foreign host.


The Oracle iPlanet Web Server 7.0 access logs would show the request for "GET" truncated to "ET":

127.0.0.1 - - [18/Mar/2010:18:39:31 -0700] "ET / HTTP/1.1" 501 148



Cause

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