<markus.alexander@gmx.at> wrote in message
news:1166532409.586582.163780@a3g2000cwd.googlegroups.com...
> 4 0.000846 192.168.1.73 192.168.1.20 HTTP
> GET / HTTP/1.1
> 5 0.001631 192.168.1.20 192.168.1.73 TCP
> [TCP segment of a reassembled PDU]
> 6 0.001664 192.168.1.20 192.168.1.73 HTTP
> HTTP/1.1 401 Unauthorized (text/html)
Please show all of the HTTP headers. My guess is that a keep-alive is not
being allowed.
When the 401 is received, the request/response pair has finished, so the
connection may be dropped at this time by either the server or the client.
In the case of TIdHTTP, it will not drop the connection at this point if you
have the hoInProcessAuth flag set in the Options property, or are using the
OnAuthorization event. When performing the next step of the authorization,
TIdHTTP will not disconnect the socket as the URL has not changed. But
there is no guarantee that the server hasn't disconnected the socket on its
end.
> 15 0.016380 192.168.1.73 192.168.1.20 HTTP
> GET / HTTP/1.1, NTLMSSP_NEGOTIATE
> 16 0.017057 192.168.1.20 192.168.1.73 TCP
> [TCP segment of a reassembled PDU]
> 17 0.017104 192.168.1.20 192.168.1.73 HTTP
> HTTP/1.1 401 Unauthorized, NTLMSSP_CHALLENGE (text/html)
> 18 0.017130 192.168.1.73 192.168.1.20 TCP
Same thing here.
> And now the same request using IE:
Since you have not shown the actual HTTP data, there is no way to compare
what Indy is sending versus what IE is sending.
Gambit
