i think the timeout is only for "some data".. perhaps if you try forking another process (that is attached to the same output handle) that keeps the connection alive by sending some data down the pipe every 30 seconds or so until you are ready to send the final bit of data... that should help...
simran. On Wed, 2004-07-14 at 09:19, Mathew Robertson wrote: > > > That looks like a generic IE error message - look at the bottom of > > > the page. It probably has something like - > > > > > > HTTP 500 - Internal server error > > > Internet Explorer > > > > > > My guess is you're timing out before the results can be served up. > > > > Grrr. You are absolutely right. I tried serving the page up in Firefox and > > it works fine. Any idea how to adjust the timeout value for IE? > > AFAIK - there is no way to adjust the timeout. It is one of the reasons reviewers > are saying "Firefox renders faster than IE". > > You could try using mod_gzip (assuming that you are using apache) - this may help if > your timeout is bandwidth related (eg viewing the page over a modem). > > Mathew > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Html-template-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/html-template-users ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Html-template-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/html-template-users
