Re: How do I close a persistent connection?

[Stas Bekman]

On 8 Sep 2001, J. Zobel wrote:

>
> Hi.
>
> We are experiencing infrequent troubles (page could not be displayed)
> with IE 5 and redirects under SSL. As a workaround (hopefully) I want to
> close the persistent HTTP/1.1 connection if such a redirect occurs.
>
> How do I do this. Sending a Connection:close header will tell the client
> that I will close the connection, but how do I actually do this?

Don't use KeepAlive with mod_perl in first place if you are talking about
mod_perl. http://perl.apache.org/guide/performance.html#KeepAlive


_
Stas Bekman  JAm_pH --   Just Another mod_perl Hacker
http://stason.org/   mod_perl Guide  http://perl.apache.org/guide
mailto:[EMAIL PROTECTED]   http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/

How do I close a persistent connection?

[J. Zobel]

Hi.

We are experiencing infrequent troubles (page could not be displayed)
with IE 5 and redirects under SSL. As a workaround (hopefully) I want to
close the persistent HTTP/1.1 connection if such a redirect occurs. 

How do I do this. Sending a Connection:close header will tell the client
that I will close the connection, but how do I actually do this?

Thanx,
Joachim

Persistent connection ?

[Deja User]

Hi all ,

   I have never done such a thing before , so would appreciate if you people could 
help me out .

   So i have a client application wanting to upload chunks of data to the webserver .

   Now the way i want this to happen is to have the client open a connection to the 
webserver ,send the headers do the initial authentication both ways and then start 
sending chunks of data ,after receiving each chunk of data the webserver (mod perl 
script) would process the data and send an acknowledgement to the client and then the 
client continues with the second upload and so on without 
the client closing the connection .

  The webserver is parsing the headers and using the rewrite rules to decide which 
script to run on the fly when the request is made , so in the above scenario this 
information would be sent just once before the upload of the first chunk of data ,so 
in short the script should somehow remain in the apache child to accept the next set 
of data .

  Could you comment on this ?

thanks,
Sachin

 





--== Sent via Deja.com ==--
http://www.deja.com/