Hello!
I ran into some problems with squid (1.1.x):
- If using the hierarchy_stoplist, it works only for GET requests, not
for
POST, CONNECT and so on. Is there a reason for this ?
What would you say to a "hierarchy_stoplist_pattern(/i)" directive
which is honored by all request types (GET, POST, CONNECT ...).
So, if you write
# Handle this direct (local domains and so on ...)
hierarchy_stoplist_pattern/i !//www.siemens.at/ //.*\.siemens.at/
//132\.10\.
in squid.conf:
- A request "GET http://www.siemens.at/page1.html" would go through
the normal
selection algorithm (and would, in my case be loaded from the
parent proxy
cause it's outside the firewall).
- A request "GET "http://ourserver.siemens.at/some/page.html" would
be handled
directly.
- A request "POST http://132.10.1.193/cgi-bin/script1.pl" would be
handled directly.
- A request "CONNECT
https://wwws.sie.siemens.at/some_secure_document" would
also be handled directly
Btw: why not put the server selection into function
icpProcessRequest?
- The Client-Authentication accepts only one domain for which
authentication is
not required. This should be more ...
Any comments ?
Greetings from Austria!
A. Lamprecht <Andreas.Lamprecht@siemens.at>
Received on Fri Jan 17 1997 - 03:55:39 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:34:06 MST