[prev in list] [next in list] [prev in thread] [next in thread] 

List:       squid-users
Subject:    Re: [squid-users] Secure ICAP
From:       Alex Rousskov <rousskov () measurement-factory ! com>
Date:       2019-05-06 23:52:17
Message-ID: c0a9a520-54a4-427e-6fbb-21da8d7227ac () measurement-factory ! com
[Download RAW message or body]

On 5/6/19 10:19 AM, TRAN DAC wrote:
> accept = 10.2.2.236:11344
> connect = 10.2.2.236:1344

> WARNING: Squid got an invalid ICAP OPTIONS response from service
> icaps://10.2.2.236:11344/request;
> error: unsupported status code of OPTIONS response

> 2019/05/06 17:50:27 kid1| essential ICAP service is down after an
> options fetch failure: icaps://10.2.2.236:11344/request  [down,!valid]/

> And from the ICAP server stunnel logs the ssl initiation worked fine but
> it can't connect to the port 1344

Why not? In other words, what prevents your stunnel from connecting to
your ICAP server? That problem seems to be unrelated to Squid or even
secure ICAP.

Alex.
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

[prev in list] [next in list] [prev in thread] [next in thread]