On 3/8/21 10:10 AM, Niels Hofmans wrote: > During testing sslbump + icap I noticed that websockets (ws + was) are > not supported by squid. (Even if using on_unsupported_protocol) > Are there any plans for supporting this with sslbump? Your question can be misinterpreted in many different ways. I will answer the following related question instead: Q: Are there any plans for Squid to send tunneled traffic through adaptation services? The ICAP and eCAP protocols cannot support opaque/messageless traffic natively. Squid can be enhanced to wrap tunneled traffic into something resembling HTTP messages so that it can be analyzed using adaptation services (e.g., Squid applies similar wrapping to FTP traffic already). I recall occasional requests for such a feature. I am not aware of anybody working on that right now. https://wiki.squid-cache.org/SquidFaq/AboutSquid#How_to_add_a_new_Squid_feature.2C_enhance.2C_of_fix_something.3F HTH, Alex. P.S. Latest Squids support forwarding websocket tunnels that use HTTP Upgrade mechanism (see http_upgrade_request_protocols in v5 squid.conf.documented). _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
