On Monday 03 March 2003 13.37, atit_ldce wrote:
> in urlParse method of url.c when request is for https protocol
>
> method will be METHOD_CONNECT
>
> now consider follwing code that i have copied from function
> if (method == METHOD_CONNECT) {
> debug(17,3) ("urlParse: Protocol %d Method %d
> \n",protocol,method); port = CONNECT_PORT;
> if (sscanf(url, "%[^:]:%d", host, &port) < 1)
> return NULL;
>
> so we have protocol = PROTO_NONE;
> why protocol is not set to PROTO_HTTPS?
Because the protocol is unknown to Squid for SSL requests.
> is there any bug? or it has special purpose for not to set protcol
> to PROTO_HTTPS
PROTO_HTTPS is reserved for when Squid has really received a https://
URL, and used for this purpose in the current Squid sources.
Squid recieves https:// URLs in two cases
a) When it is used as a SSL enabled accelerator (https_port
directive).
b) When Squid is used as a SSL gateway for HTTP clients not natively
supporting SSL, such as old versions of LYNX etc..
And actually also a third case which should not happen...
c) When brosers bug out and reuses a plain unencrypted http proxy
connection for https:// requests.. many versions of Netscape 4.X is
known to do this..
Regards
Henrik
