Ah... I found out the problem (as to Access Denied)...
Somehow I've forgotten to include ProxyC in an http_access statement in
ProxyA...
All is well now...
Thanks for your kind assistance, Amos! :-)
Rgds
[p]
Amos Jeffries wrote:
Pandu E Poluan wrote:
Without "allow-miss", I get the error
Pandu E Poluan wrote:
Without "allow-miss", I get the error:
*Valid document was not found in the cache and only-if-cached directive
was specified.*
Okay, bet use it then. Should be safe enough in your setup.
Amos
Strangely, doing the same on ProxyC causes an "Access Denied" error...
Rgd
Without "allow-miss", I get the error:
*Valid document was not found in the cache and only-if-cached directive
was specified.*
Strangely, doing the same on ProxyC causes an "Access Denied" error...
Rgds
[p]
Amos Jeffries wrote:
Pandu E Poluan wrote:
Okay, some experimentations I made:
I
Pandu E Poluan wrote:
Okay, some experimentations I made:
I added the following lines on ProxyB:
# lines from Amos' tip
acl fastsites dstdomain .need-fast-inet.com
acl fastsites dstdomain .another-need-fast-inet.com
never_direct allow fastsites
Changes on ProxyA:
# lines from Amos' tip
acl fa
Okay, some experimentations I made:
I added the following lines on ProxyB:
# lines from Amos' tip
acl fastsites dstdomain .need-fast-inet.com
acl fastsites dstdomain .another-need-fast-inet.com
never_direct allow fastsites
Changes on ProxyA:
# lines from Amos' tip
acl fastsites dstdomain .need
Pandu E Poluan wrote:
Hmmm... strange...
Now, instead of accessing the site objectX, ProxyB and ProxyC users
can't access the site at all...
But no SQUID error page shows up... the browser simply times out...
Accessing URLs other thatn objectX still works...
objectX is accessible via Proxy
Pandu E Poluan wrote:
Hmmm... strange...
Now, instead of accessing the site objectX, ProxyB and ProxyC users
can't access the site at all...
But no SQUID error page shows up... the browser simply times out...
Accessing URLs other thatn objectX still works...
objectX is accessible via Proxy
Hmmm... strange...
Now, instead of accessing the site objectX, ProxyB and ProxyC users
can't access the site at all...
But no SQUID error page shows up... the browser simply times out...
Accessing URLs other thatn objectX still works...
objectX is accessible via ProxyA, though.
The changes
Aha! Thanks a lot, Amos :-)
I have been suspicious all along that the solution uses miss_access and
never_direct ... but never saw an example anywhere.
Again, much thanks!
** rushes to his proxies to configure them **
Rgds.
[p]
Amos Jeffries wrote:
Pandu E Poluan wrote:
The URL is all
Pandu E Poluan wrote:
The URL is allowed to be accessed by everyone, ProxyA-users, and
ProxyB/C-users alike.
I just want the URL to be retrieved by ProxyA, because accessing that
certain URL through ProxyB/C is too damn slow (pardon the language).
Rgds.
Okay. Thought it might be somethin
Pandu E Poluan wrote:
Anyone care to comment on my email?
And another question: Is it possible to use miss_access with a dstdomain
acl?
Rgds.
Pandu E Poluan wrote:
Hi,
I want to know is there a way to force a URL to be retrieved by only a
certain proxy, while ensuring that meshing works
Anyone care to comment on my email?
And another question: Is it possible to use miss_access with a dstdomain
acl?
Rgds.
Pandu E Poluan wrote:
Hi,
I want to know is there a way to force a URL to be retrieved by only a
certain proxy, while ensuring that meshing works.
Here's the scenario
12 matches
Mail list logo