I've noticed that openufp works well acting as websense server frontend to process HTTP onto the Squid Proxy.
HTTPS however returns a 'request type not known, closing connecion'. I envisage this has something to do with Squid processing HTTP on one listening port and HTTPS on another.
server:
openufp openufp[20128]: received url request - Original URL: http://www.google.com/
openufp[20128]: proxy: result (HTTP/1.1 301 Moved Permanently#...
server:
openufp[20130]: request type not known, closing connecion.
Is it possible the different listeners could be integrated into openufp? i.e.
if http {url_check{proxip_ip proxy_port} elseif https { url_check{proxy_ip:proxy_port_https }
I've noticed that openufp works well acting as websense server frontend to process HTTP onto the Squid Proxy.
HTTPS however returns a 'request type not known, closing connecion'. I envisage this has something to do with Squid processing HTTP on one listening port and HTTPS on another.
i.e. using HTTP client: curl http://www.google.com
server: openufp openufp[20128]: received url request - Original URL: http://www.google.com/ openufp[20128]: proxy: result (HTTP/1.1 301 Moved Permanently#...
using HTTPS client: curl https://www.google.com
server: openufp[20130]: request type not known, closing connecion.
Is it possible the different listeners could be integrated into openufp? i.e. if http {url_check{proxip_ip proxy_port} elseif https { url_check{proxy_ip:proxy_port_https }