Environment
Novell Access Management 3 Linux Access Gateway
Situation
Accessing Web based email system via Linux Access Gateway (LAG).
All works fine with the exception of attachments, which appear to
be truncated when viewed at the client side. By forcing HTTP 1.0 to
the origin server, the problem can be worked around as compression
is disabled.
The traces show that the request is satisfied by the origin server and the document is always returned within a single chunk of HTTP data. The LAG processes this request and returns the document to the browser within a large number of chunks.The data returned to the browser, when it fails, is always missing some of the data.
The traces show that the request is satisfied by the origin server and the document is always returned within a single chunk of HTTP data. The LAG processes this request and returns the document to the browser within a large number of chunks.The data returned to the browser, when it fails, is always missing some of the data.
Resolution
Apply LAG update in nam3sp1ir3.tar.gz (Access Manager 3 Support
Pack 1 Interim Release 3). The problem stemmed from the fact that
the webserver was breaking the RFC. This web server was sending us
the chunk response without sending the zero length chunk at the
end, but just closing the connection by sending a TCP FIN instead.
LAG expects the zero length chunk to say it as the end of chunk
response. With the latest code change, we added logic to consider
FIN as the end of the chunk response.