Re:Re: Puzzled at "clientProcessRequest". :-(

From: <maer727@dont-contact.us>
Date: Thu, 18 Apr 2002 10:30:04 +0800 (CST)

Thanks, Henrik pal!

You have clarified all my doubts. :-)

Best regards
George, Ma

----- Original Message -----
From: Henrik Nordstrom
To: maer727@sohu.com
Cc: squid-dev@squid-cache.org
Subject: Re: Puzzled at "clientProcessRequest". :-(
Sent: Thu Apr 18 05:26:10 CST 2002

> TRACE is a special method. It can by definition never be a HIT. See
> RFC2616 for a definition of the meaning of the TRACE method. The code
> becomes clearer if you know what the code is trying to accomplish.
>
> Note: the TRACE clientCreateStoreEntry is within a if statement, not
> always true.
>
> All methods mentioned in Squid except for the PURGE method is defined by
> Internet RFC documents or Internet Drafts. PURGE is a Squid specific
> method documented in the Squid FAQ.
>
> Regards
> Henrik
>
>
>
>
> maer727@sohu.com wrote:
> >
> > Thanks, Henrik pal!
> >
> > I have downloaded the Squid-2.5.PRE6. My question resides in client_side.c,
> > line 2302. In function, clientProcessRequest, there are several cases to check.
> > They are METHOD_CONNECT, METHOD_PURGE, METHOD_TRACE, and else. When case METHOD_TRACE
> > occurs, it is certain that cache will miss, since clientCreateStoreEntry is called.
> > (I think clientCreateStoreEntry is a routine to implement cache miss.)
> >
> > My question is, why when METHOD_TRACE request occurs, the cache will certainly miss the
> > hit. What is the reason between cache miss and METHOD_TRACE request? What does
> > METHOD_TRACE request mean?
> >
> > Best regards,
> > George, Ma
Received on Wed Apr 17 2002 - 20:40:10 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:15:12 MST