Cannot force HTTP 1.0 communication to Back end Web server with Linux Access Gateway

  • 3395345
  • 29-May-2007
  • 26-Apr-2012


Novell Access Management 3 Linux Access Gateway
Novell Access Manager 3 Support Pack 1 Beta 1 applied


Linux Access Gateway (LAG) setup to accelerate a Portal Web server. The Portal Web server compressed and chunked the responses coming back from the Web server. The problem was that the Web server would frequently advertise a certain amount of chunked data to be sent back, without sending the full amount of data back. The end result would be a 504 gateway timeout error being displayed on the browser after the data read timeout (default 120 seconds) was exceeded.

To work around the issue on the Web server, we decided to force HTTP 1.0 request to the Web server (HTTP options under Web server TAB) so that the Accept-encoding types would not include any chunked or compressed requests and the Web server would return basic data. As soon as we changed and applied the setting to force HTTP 1.0 to origin server, the monitored requests going to the web server continued to be HTTP 1.1.


Fixed in Support Pack 1 beta 2 build and onwards.