[WEB4LIB] MSIE5.0 and CGI scripts timing out - URL

[rpage at Okstate.edu]

Hi! I just tried the URL, several times, using IE5 (on NT) and had a couple of
timeouts and a couple of completes (all the way to the "Link to the main HEP
(SPIRES-SLAC) page" message). I'm only guessing, but maybe there is something
else timing out somewhere.

--Richard

 Richard M. Page                   | Voice      (405) 744-5347
 Head, Library Systems Department        | Fax        (405) 744-7579
 224A Library, Oklahoma State University      |
 Stillwater, OK 74078-1070               | E-Mail: rpage at okstate.edu
=+=+=+=+=+=+=+=+=+=+= http://el0455.lib.okstate.edu/ =+=+=+=+=+=+=+=+=+=+=+=

                                                              
                                                              
                                                              
 To:      Multiple recipients of list                         
          <web4lib at webjunction.org>                      
                                                              
                                                              
                                                              
                                                              
                                                              
 Subject: [WEB4LIB] MSIE5.0 and CGI scripts timing out - URL  
                                                              




Some people asked for a URL to see for themselves. Here's one:

http://www.slac.stanford.edu/cgi-bin/spiface/find/hep/www?rawcmd=find+author
+drell+and+date+1998&FORMAT=WWW&SEQUENCE=

>I am wondering if anyone has run into a similar problem.
>
>We have some home grown CGI scripts that, when someone uses the new MS
>Internet Explorer 5.0, they just time out. Never had this problem with any
>other browser client, but am now getting this problem with MSIE5.0.
>
>The CGI scripts can take a long time (> 10 seconds) to return data, and in
>that time, MSIE5.0 will time out, and just stop... only returning the HTML
>code that had been sent down the pike up until that point.
>
>Or does someone have any suggestions for keeping the connection alive?