Netscape 6 connection timeout

[lisakriel]

Hi we are using Weblogic Server 5.x sp 10 at a client who is an transnational company and can only upgrade to the next version when all the existing aplications in the various countries have been tested (and if necessary modified to work with the current release).

Our application which works fine in Internet Explorer 5 upwards, keeps getting the following error in Netscape 6. Netscape 4 compatibility is not a requirement for this application so no testing has been done on this.

The error that occurs is:


Error 400--Bad Request


From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:


10.4.1 400 Bad Request


The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
--------------------------------
Sometimes refreshing the screen/reloading the page solves the problem. By running tools to intercept the calls to the server we were able to determine that this problem occurs when the connection is dropped before the header string length information is passed. Thus only partial information is received and therefor cannot be processed.

Calls are jsp post.

Is there any way of persisting a connection between the browser and server, or any way of setting the time out elapsed time to a longer time?

thanks
Lisa

 

[wushutwist]

Just for completeness you might want to try placing a proxy server in front of your Application Server. WebLogic supports Apache, Iplanet, and IIS as proxies. All of these servers support Keep-Alive Connections and I would think you problem would then disappear. Sorry I can't help more but I am not very familiar with WebLogic 5.1 (I have only used it on one project).

The other solution is to upgrade to WebLogic 6.1 where I have never encountered this problem. Unfortunately this doesn't seem to be an option for you.