> what is your test client?
I wrote a command line client that just sends/receives basic messages for testing.
I have been opening a socket and sending this:
GET /perl/myscript HTTP/1.1
Connection: Keep-Alive
Host: myhost.mydomain.com\n\n
It worked as expected - I was able to keep the socket open and send & receive
multiple
messages. When I set PerlSendHeader to Off, the socket closed after the 1st query.
I finally had success with socket persistence when I tried using CGI to print the
header
by replacing this:
print "Content-type: text/html\n\n";
with this:
print header();
Once I changed how I was printing the header from the script, the socket
persistence
worked with PerlSendHeader Off. So I guess I solved my problem although I don't
really
know why.
Brian
Doug MacEachern wrote:
> On Wed, 27 Sep 2000, B. Burke wrote:
>
> > When I set PerlSendHeader to Off in my perl.conf it doesn't send headers,
> > which
> > is good. The bad part is that it seems to break socket persistence for some
> > reason.
> > When I have PerlSendHeader set to On, I can open a socket with my test client,
> >
> > and make multiple queries on the same socket.
>
> what is your test client? apache will close the connection after the
> first request, unless keep-alive is maintained between client/server.
