David Schwartz wrote:
Notice the two persistent connection headers returned? And, in practice,
the connection is in fact persistent. If you were correct, the server would
ignore the "Connection" header since it "has no meaning". Try it without a
connection header and you will see the dif
Hello,
> > To clarify: HTTP 1.0 do not have persistent connection so "connection"
> > has no meaning for HTTP 1.0 and server should drop connection after
> > servicing such client request.
>
> This is true under the official specification, but is not true as to how
> the protocol is used. Pe
> To clarify: HTTP 1.0 do not have persistent connection so "connection"
> has no meaning for HTTP 1.0 and server should drop connection after
> servicing such client request.
This is true under the official specification, but is not true as to how
the protocol is used. Persistent connect
Hello,
> For some reason I didn't get the original post, so I'm replying to the
> reply.
>
> > In a blocking socket when a network read freezes, it
> > is normal. It only means that nothing arrived on the
> > socket.
> >
> > You got to take a look at the MSN protocol. With HTTP,
> > it might
For some reason I didn't get the original post, so I'm replying to the
reply.
> In a blocking socket when a network read freezes, it
> is normal. It only means that nothing arrived on the
> socket.
>
> You got to take a look at the MSN protocol. With HTTP,
> it might be sending a TCP FIN
In a blocking socket when a network read freezes, it
is normal. It only means that nothing arrived on the
socket.
You got to take a look at the MSN protocol. With HTTP,
it might be sending a TCP FIN or something which is
why it is working in that case...
--- Robert Olsson <[EMAIL PROTECTED]> wro
Hi,
I'm using openssl for the very first time, developing a chat client
(for the MSN Messenger protocol) and have
now stumbled across a problem regarding blocking sockets. Basically,
when receiving data from the server
after each request, I loop BIO_read until it returns a value <= 0.
The pr
