On 9 Oct 2008 at 14:16, Christopher Schultz wrote:
Maurizio,
Christopher,
Maurizio Lotauro wrote:
On 6 Oct 2008 at 14:58, Christopher Schultz wrote:
[...]
If you are writing network code, you need to handle disconnects at
any time.
This is handled, but in that case there is no need to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maurizio,
Maurizio Lotauro wrote:
On 6 Oct 2008 at 14:58, Christopher Schultz wrote:
Is it a problem to get this 401 before the request is complete?
In my case it was a problem because the receive of the server response
trigger an end of
On 6 Oct 2008 at 14:58, Christopher Schultz wrote:
Maurizio,
Christofer,
Maurizio Lotauro wrote:
I already read this rfc and now I have read it again, but I'm
unable to found where it
describe that the server can answer with 401 before the client has
finished to send all data.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maurizio,
Maurizio Lotauro wrote:
I already read this rfc and now I have read it again, but I'm unable to found
where it
describe that the server can answer with 401 before the client has finished
to send all data.
There's nothing that says
On 30 Sep 2008 at 18:27, Caldarale, Charles R wrote:
From: Maurizio Lotauro
[mailto:[EMAIL PROTECTED]
Subject: Authentication behaviour
The server answers with 401 before it has received the
whole content send from client. In fact it seems that
the answer become right after the
From: Maurizio Lotauro
[mailto:[EMAIL PROTECTED]
Subject: Authentication behaviour
The server answers with 401 before it has received the
whole content send from client. In fact it seems that
the answer become right after the server has received
the http header.
Looks proper to me for
