# TLS/SSL bumping steps ssl_bump peek tls_s1_connect all # peek at TLS/SSL connect data ssl_bump splice all # splice: no active bumping on_unsupported_protocol tunnel all
pinger_enable off digest_generation off netdb_filename none ipcache_size 128 fqdncache_size 128 via off forwarded_for transparent httpd_suppress_version_string on cache deny all cache_mem 0 MB memory_pools off shutdown_lifetime 0 seconds
#logfile_daemon /dev/null access_log none
#acl good_url dstdomain .yahoo.com http_access allow all
Re: Squid url rewriters creating issues in case of multi-threaded mode
On 7/08/19 6:40 pm, Chirayu Patel wrote:
> url_rewrite_program /tmp/squid/urlcat_server
> url_rewrite_children 15 startup=1 idle=1 concurrency=30 queue-size=10000
> url_rewrite_extras "%>a %lp %ssl::>sni"
> --> I have a single process which receives the requests in
> multi-threaded mode
> --> The issue I am facing right now is, I am continuously getting these
> messages :
> Tue Aug 6 15:33:09 2019 daemon.notice squid: helperHandleRead:
> unexpected reply on channel 0 from redirector #Hlpr1 '176 OK'
It looks like your helper is trying to indicate channel-ID 176 but
sending something that is not a digit before the ID number.
Can you run the helper manually and send it one or a bunch of requests
to see if it is producing the correct output?
Is there any whitespace or prefix before the channel-ID it is putting on
the line? The above log entry looks like the helper is producing
something like these:
"0 178 OK"
" 178 OK"