Maurizio,
Is this test server the Tomcat server where the issue
manifested before?
==== QUOTE:
At this point the problem seems quite different. The
"early" receive of the 401
interrupt the sending of the body. So the server
"drop" what receive until the
content length is reached, and then consider the rest
as a new request.
=== END
I'm not sure I understand. Do you mean that the
server did send an early 401 response but allowed the
client to send up to Content-Length-amount of data?
So, then there's no problem, right? I though that as
soon as it sent the response, all the rest of the
request (the body) was being treated as a new request
from the server and failing as invalid. Unless you
were sending more data than you specified in the
Content-Length before...
I'm confused. I don't have access to WireShark right
now, so I can't really test this at the moment.
-dZ.
>------- Original Message -------
>From : Maurizio
Lotauro[mailto:[EMAIL PROTECTED]
>Sent : 9/23/2008 12:32:24 PM
>To : [email protected]
>Cc :
>Subject : RE: Re: [twsocket] Early web server response
>
>Scrive Maurizio Lotauro <[EMAIL PROTECTED]>:
> Scrive DZ-Jay <[EMAIL PROTECTED]>:
[...]
> > In any case, I'll see if I can do some
experiments with IE and Tomcat
> > and let you know what I find.
>
> Please wait, I asked to our server admin to prepare
a test environment
> public
> available (I need it for myself). Probably it will
be ready tomorrow.
I have a public server that show the problem. Who is
interested write me an email.
I made some test with a test application and IE. The
latter works.
Analyzing the communication with WireShark it seems
that it works because IE
complete to send the whole body before resend the
request including the
authorization info.
At this point the problem seems quite different. The
"early" receive of the 401
interrupt the sending of the body. So the server
"drop" what receive until the
content length is reached, and then consider the rest
as a new request.
I have a modified version of THttpCli that show
automatically a user/pwd request
when the status code is 401/407 (and cache it). In
fact if I wait to give user
and pwd then it works because in the meantime the
whole body is sent.
So the solution seems wait that the body is sent
before retrying.
Bye, Maurizio.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
