ERR_ICAP_FAILURE without loadable_modules
I have tried the first following configuration on the system :
Squid Version: squid-3.4.5; sample-0.2.1; libecap-0.2.0 | Also tried squid-3.5.21; Libecap-1.0.0; libecap-
OS: Centos 6 64 bits
VMware: 6.
Then I follow the guideline from this URL, to test out how ecap works: http://
The first Scenario of replacing "the" word to "a" word.
Here is the configuration & test result is as what the guideline tells:
Squid.conf: This test result is OK, worked as expected.
=======
loadable_modules /usr/local/
ecap_enable on
ecap_service ecapModifier respmod_precache
uri = ECAP: //e-cap.
the victim = the
replacement = a
adaptation_access ecapModifier allow all
accept-Encoding request_
=======
The second scenario, is to, inject the javascript into the squid cache, however, with the guideline & sample configuration from the site gave me error.
Squid.conf: Test is NOT OK
=======
ecap_enable on
ecap_service ecapModifier respmod_precache
uri = ECAP: //e-cap.
victim = </ body> \
adaptation_access ecapModifier allow all
=======
Here is the completed configuration file that we are currently using:
Config file squid.conf
#
# Recommended minimum configuration:
#
# Example rule either, allowing local access networks khỏi.
# Adapt to list ngôn (internal) IP networks from where browsing
# Shouldnt be allowed
#acl localnet src # RFC1918 possible The internal network 10.0.0.0/8
#acl localnet src # RFC1918 possible The internal network 172.16.0.0/12
localnet acl src # RFC1918 possible The internal network 192.168.4.0/24
src localnet #acl fc00 :: / 7 # RFC 4193 private local network range
src localnet #acl fe80 :: / 10 link-local # RFC 4291 machines
acl SSL_ports port 443
acl Safe_ports # http port 80
acl Safe_ports 21 # ftp port
# https port 443 acl Safe_ports
acl port Safe_ports 70 # gopher
acl port Safe_ports 210 # wais
Unregistered Safe_ports acl ports port # 1025-65535
acl Safe_ports 280 # http-mgmt port
acl Safe_ports 488 # GSS-http port
acl port Safe_ports 591 # FileMaker
acl 777 # MultiLing http port Safe_ports
acl CONNECT CONNECT method
#
# Recommended minimum configuration Access Permission:
#
# Deny requests to Certain unsafe ports
http_access deny! Safe_ports
# Deny CONNECT to other coal ports SSL secure
http_access deny CONNECT! SSL_ports
# Only allow access from localhost cachemgr
http_access allow manager localhost
http_access deny manager
We Strongly recommend # sau be uncommented to protect innocent
# Web applications running on the proxy server who think the only
# One who can access services on "localhost" is a local user
#http_access deny to_localhost
#
# INSERT YOUR OWN RULE (S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#
# Example rule either, allowing local access networks khỏi.
# Adapt localnet in the ACL section to list ngôn (internal) IP networks
From where browsing # shouldnt be allowed
http_access allow localnet
http_access allow localhost
# And finally deny all other access to this proxy
http_access deny all
Listens to port Squid thường # 3128
#http_port 3128
3128 http_port transparent
SSL #config
3129 https_port transparent connection ssl-bump-auth = off generate-
sslcrtd_program /usr/lib64/
sslcrtd_children 50 idle startup = 5 = 1
ssl_bump none localhost
sslproxy_cert_error allow all
sslproxy_flags DONT_VERIFY_PEER
always_direct allow all
# Uncomment and adjust on the drop to add a disk cache directory.
#cache_dir ufs /var/cache/ squid 100 16 256
cache_dir ufs /var/cache/ squid 10000 32 512
# Leave coredumps in the first cache dir
coredump_dir /var/cache/squid
#
# Add any of Your Own những refresh_pattern above entries.
#
refresh_pattern ^ ftp: 1440 20% 10080
refresh_pattern ^ gopher: 1440 1440 0%
refresh_pattern -i (/ cgi-bin / | \?) 0 0% 0
refresh_pattern. 0 20% 4320
ecap_enable on
ecap_service ecapModifier respmod_precache \
uri = ECAP: //e-cap.
victim = </ body> \
adaptation_access ecapModifier allow all
=======
Compiled the Squid with the following parameters in order to enable the modules as following:
[root@XXX]# squid -v
Squid Cache: Version 3.4.5
configure options: '--program-prefix=' '--prefix=/usr' '--exec-
When browsing on the browser, the Browser returns :
The following error was encountered while trying to retrieve the URL
ICAP protocal error
The system returned: [No Error]
This means that some aspect of the ICAP communication failed
Some possible problems are:
The ICAP server is not reachable
An Illegal response was received from the ICAP server
=======
Thanks,
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- eCAP Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask Bùi Huy Long for more information if necessary.