tor 2003-01-16 klockan 09.35 skrev Kinkie:
> We didn't really make it stateless, we just thought it best to leave as
> much status as possible in the client. One problem we have is that it's
> guarranteed that the connection to the client will be shut down between the
> negotiate and challenge phases, because we shut it down.
???
To my knowledge we only shut down the connection in the proposal packet,
before NTLMSSP starts. Once the negotiate packet has been received from
the client the connection is kept persistent.
Client->Squid Initial request
Squid->Client NTLM/Basic proposal. Connection terminated.
Client->Squid NTLMSSP negotiate. Persistent. Not currently sent to
helpers.
Squid->Client NTLMSSP challenge from helper.. Persistent
Client->Squid NTLMSSP authenticate to helper. Persistent.
Squid->Client Response. Persistent (if possible).
Client->Squid Next request. Persistent
Squid->Client Next Response. Persistent (if possible).
The termination after the authentication proposal is quite likely
unnecessary and causes a bit of problems with request entities
currently.. (but the real cause to these problems needs to be fixed
anyway, making it persistent only hides the real problem there).
Regards
Henrik
Received on Thu Jan 16 2003 - 03:01:17 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:19:06 MST