Re: Authentication behaviour

2008-10-10 Thread Maurizio Lotauro
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

Re: Authentication behaviour

2008-10-08 Thread Maurizio Lotauro
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

RE: Authentication behaviour

2008-10-01 Thread Maurizio Lotauro
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

Authentication behaviour

2008-09-30 Thread Maurizio Lotauro
Hello, I'm writing an http client application. When on the server Tomcat is configured to require an authentication (basic) my client raise a strange error. If authentication is disabled then it works fine. I analyzed the communication using WireShark and I noticed a strange behaviour. The