I think all the webex stuff is still done over https for the actual sessions so I would say blocking CONNECT or port 443 should achieve the desired results. Regular http should still access as expected. Something along the lines of acl webex dstdomain .webex.com #Add a custom error message to let the end customer know why they arent able to get out to webex # and how to get out if they absolutely need to. #place deny_webex in /etc/squid/error/ or /usr/share/squid/errors/English #deny_info ERR_DENY_WEBEX deny_webex http_access deny CONNECT webex On Jan 9, 2008 12:45 AM, Nadeem Semaan <nadeem_semaan@xxxxxxxxx> wrote: > Hello everyone, > > anyone know a way of blocking webex without blocking the actual site? I mean I still want users to read about it (even on the official website), I just dont want them to be able to use it without prior permission. > > Thanks and Happy New Year > > > ____________________________________________________________________________________ > Never miss a thing. Make Yahoo your home page. > http://www.yahoo.com/r/hs >
