Bug 57973
Summary: | Squid doesn't work with config directive cache_peer | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <jurek> |
Component: | squid | Assignee: | Martin Stransky <stransky> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | jurek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-13 13:02:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2002-01-03 21:48:46 UTC
Other important configuration lines are always_direct and never_direct. I'm sure it is not a bug with the Redhat RPM as I have been using these RPM's for many months now in a production environment and cannot replicate this problem. Have you tried the latest release from ftp://rawhide.redhat.com/pub/redhat/linux/rawhide/i386/RedHat/RPMS/squid- 2.4.STABLE2-4.i386.rpm ?? You may also want to look for advice on the squid-users mailing list: http://www.squid-cache.org/Doc/FAQ/FAQ-1.html#ss1.9 When you want to work Squid as proxy to proxy connections (cache_peer) squid do corectly all unsecured (http) connections but all secured (https) connection goes direct (allways). Have you checked the new versions of squid? |