Hello Amos, ---------------------------------------- > To: squid-users@xxxxxxxxxxxxxxx > Date: Thu, 9 Jun 2011 13:02:49 +1200 > From: squid3@xxxxxxxxxxxxx > Subject: Re: FW: Why doesn't REQUEST_HEADER_ACCESS work properly with aclnames? > > On Wed, 8 Jun 2011 17:01:39 +0000, Jenny Lee wrote: > > I just realized that "Cookie" headers are also not obeyed when going > > through peers. > > > > Everything works going direct, but nothing works if you are using any > > peers. > > > > I surely cannot be the only person out of all squid users that is > > bitten by this anomaly. > > > > Jenny > > > > Possibly not. Although most of the "anonymous" crowd just put "all" ACL > by instinct and leave it at that. Yes but this is not a server for 1 person. I block cookies, but I want to allow my OFFICE to pass cookies through. It seems like nothing except "all" works on this HEADER_ACCESS lines. Anything else has empty value and fails. 2011/06/08 22:50:26.271 kid1| ACLList::matches: checking all 2011/06/08 22:50:26.271 kid1| ACL::checklistMatches: checking 'all' 2011/06/08 22:50:26.271 kid1| aclIpAddrNetworkCompare: compare: [::]/[::] ([::]) vs [::]-[::]/[::] 2011/06/08 22:50:26.271 kid1| aclIpMatchIp: '[::]' found 2011/06/08 22:50:26.271 kid1| ACL::ChecklistMatches: result for 'all' is 1 2011/06/08 22:50:26.271 kid1| ACLList::matches: result is true 2011/06/08 22:50:26.271 kid1| aclmatchAclList: 0x7fff4e4885d0 returning true (AND list satisfied) > Did you check if 3.2.0.8 for the myportname problem? I browsed through Changelog for 3.2.0.8 but did not see any of my bugs addressed. I did not have myportname issue. > On the Cookie: header. Is the content coming from the peer cached? > Cookies are erased on cached HITs. httpSendRequest is not sending cookies to peers if "allow all" is not specified. Caching is disabled, proxy-only peers. Thanks. Jenny