Hello: We encountered a strange problem lately, and I hope we can get some help here. We are using JRun (3.02) on solaris which connect to IPlanet Web Server (4.1). We have a servlet take user request for pdf download and serve the file dynamically. We found something interesting in the http header sent back to the browser: HTTP/1.1 200 OK Server: Netscape-Enterprise/4.1 Date: Fri, 23 Feb 2001 20:59:46 GMT Connection: Close Content-Disposition: filename="prl0007.pdf" Content-type: application/pdf Content-length: 40103 Connection: close Looks like JRun set the first "Connection:Close" (in the header above), and web server set the second one. The combination of the two happens to cause problems in Microsoft Internet Explorer (5.0 above). For some reason if the MSIE get the header with two connection close statments, it will not close the connection, instead, it does the opposite: treating the connection as keep-alive connection. So even after the file is completely download to the local machine, the browser will not close the connection and start the helper program(acrobat reader) until the connection is close at the server side when the KeepAliveTimeOut is reached. It produces a long waiting time for MSIE user to download pdf file. I've been doing various tests trying to find a good work-around with this problem. One thing I noticed is that JRun set "Connection: Keep-alive" header for some jsps and servlets I run. In the situation like that, the MSIE seems working fine. So here are my questions: 1) In what condition, JRun set the header "Connection:Close" or "Connection:Keep-alive" 2) Is there way to config or inform JRun engine not sending "Connection:Close" header? Yingxia Wang Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
