# 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
> --> We are getting this error sometimes and squid crashes later :
> Tue Aug 13 15:02:12 2019 squid: helperHandleRead: unexpected reply on channel 0 from redirector #Hlpr1 '1167 OK status=302 url=https://xxx.xxx.xxx' > Tue Aug 13 15:02:12 2019 squid: assertion failed: helper.cc:1039: "skip == 0 && eom == NULL"
Most likely, Squid got a malformed (from Squid point of view) helper
response and crashed while handling it. It is not clear to me whether
the response reported on the first line is the one that led to the
crash, but neither of those lines should be printed if everything works
The parsing code for helper responses is pretty bad, but it may be
possible to figure out what caused the assertion by examining the core
dump. If you have it (or can change your environment to produce core
dumps), then please post a backtrace from gdb. Squid wiki has
instructions if you are not familiar with the process. You may prefer to
move this triage to Squid Bugzilla though.