On Monday 10 December 2001 11:54 pm, Colin Campbell wrote:
=> Hi,
=>
=> On Mon, 10 Dec 2001, --==[bman]==-- wrote:
=>
=> > O.K. I'm going bananas here. I wonder if this is a "known" issue
related to => > Microsoft products not working the same across their OSes or
it's a bug (do I => > dare to say in ... Squid)?
=>
=> No. A misunderstanding probably.
Probably...
=>
=> > Here is a deal: I have a directive in my squid.conf file:
=> >
=> > acl local-intranet dstdomain .foo.net
=> > always_direct allow local-intranet
=>
=> This is telling squid to never use a parent cache for "local-intranet". It
=> has nothing to do with a browser going direct or not. Squid cannot tell a
=> browser not to use squid. The browser must be configured to not use the
=> proxy for certain domains.
=>
=> > where .foo.net is my local intranet domain. I want my proxy to send web
=>
=> Not a squid problem. It's the browser that needs to be configured to go
=> direct.
I'm not sure. I would not post this message if I did not do my homework. On
Win.x running IE, I deliberately unchecked "bypass proxy for local sites." I
even went one step further and removed anything that would have my local
domain in it. Guess what? I went directly to the local domain web site as
it was supposed to (or as it was supposed to be handled by Squid). It's not
the case, however, with Y2K.
=>
=> > When looking into my access.log file, I have noticed that when IE runs
on => > Windows.x and makes a request to a local domain, it does not
register with my => > logs. However, when a web browser makes a request to
a local domain from => > Y2K, I can see a corresponding entry with
DIRECT/.foo.net -- directive in it. =>
=> Yes. The Windows.X browsers have been configured not to use squid. The
=> Win2K browser has not.
Wrong. I can't believe that you jumped right away to a conclusion and
assumed what has been or has not been configured on my browsers. Read my
comments above, please.
=>
=> >
=> > What am I missing here? I REALLY would have to make sure that IE on Y2K
goes => > directly to the local sites (of course, there is also the client's
side and => > it can be taken care of that way but proxy solution would seem
so much better => > because no additional setup would have to be done with
client's browser to => > facilitate NTLM compatibility....
=>
=> It has nothing to do with squid. It is a browser configuration issue. A
=> proxy cannot tell a browser not to use the proxy.
=>
=> Colin
=>
One thing you are right about is that the semantics of configuration file
comments are confusing. The following syntax:
always_direct allow
I read just like that: always direct. No second guessing. Always direct
means to me "always direct". Obviously, as I quickly begin to learn it,
there are other meanings to the word "direct"... :-)
-- Bolek, URL: http://www.bolek.com e-mail: bman@bolek.com ICQ: 4086197, Address: 402905326Received on Mon Dec 10 2001 - 22:08:38 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:05:18 MST