me myself and i

You mean we are the only ones who use your business product behind a proxy? I don't understand what makes our situation so different from others.

Hello, the first birthday of my post (see below) is getting closer. Still no solution? Best

One month later... still nothing new?

Hi Posolsvetla still nothing new? Best

Ok. Thanks.

No idea?

well... i talked about the email notification for the admin, not about Webpage customizing may i should repeat it in the text next time, i only wrote it in the topic.

Hi all, is it possible to specify the URL category in the text of the email when web control blocks a web page? If this variable is not supported, are there any plans to support this variable in the future? Best

Hi MartinK Thanks for the update! works like a charm! Good job. Thank you. Best

Hi Posolsvetla any news for me regarding this issue/bug? Best

Hi MartinK any news for me regarding this issue/bug? Best

wow.... sounds like a bonus for me *smile* and since it is the second error (see here) there is perhaps a double bonus? *double-smile* what are the next steps? Will you inform me when the problem is solved?

..and Edge, and Vivaldi... is there a browser where it works? if I understand correctly, this does not work anywhere? are we the only company using ESET and a proxy? Best Stefan

@itman this is what I expect to see this is what i get when accessing https sites from a blocked category:

unfortunately wrong The proxy runs in explicit mode on a custom port

Okay, if i can help you, please let me know. Will you get back to me as soon as you've figured out what the problem is? (hopefully with a solution?)

Hi itman, as i am on vacation today I'll get back to this tomorrow. Just a quick question: are you able to watch the video i uploaded? Best

No, the notification is from ESET. why should the WSA block that traffic? there are no blocking rules in WSA defined.

ok... may i need some help here to understand... If the website is in a category which is not blocked, all is fine (via the proxy) If the website is in a category which is blocked, it is blocked (via the proxy) and i (the administrator) receive an email notification about the blocking like: 2/3/2021 17:27:09 PM - During execution of on the computer XYZ, the following event occurred: Web control: Web page blocked by category rule. URL: hxxp://WHATEVER-IS_BLOCKED.COM:443 for me it looks like the website is blocked absolutly fine... the only thing what is not showing up is the blocking page in the browser. Assuming that the blocking page is stored localy on the client, how can that be an issue with the cisco or the bluecoat? pls help me to understand... i'm a bit lost.

Yes, thank you for the hint, but we need it location based, not time based.

Hi itman, that's what I thought at first too, but.... if I configure the client to use the bluecoat proxy that passes https requests through, it's exactly the same behavior on the client. So I don't think it has anything to do with the WSA itself. That's why I think it's an Eset problem if the Eset is behind a proxy (any proxy). As mentioned before, ESET is able to block the page (I receive an email about it), it's just not able to display the blocking page.

Description: use of Webcontrol depending on location Detail: we dont wnat that the users access specific sites if they are in the office (like shopping, gaming,...) but we don't care if they do it in their leisure time at home. Therefore a networkbased policy would be great!

here they are... ees_logs.zip

will do as soon as possible

All other (not blocked) https sites work well. If i disable Webcontrol i can reach the unwantet websites and can open them (http and https) Thats why i assume it is not an issue of the proxy. Regarding Firefox, and Chrome Error: ERR_TUNNEL_CONNECTION_FAILED As i stated before it happens in all browsers (the error messages vary) In my initial post i already pointet out that this is the message from Chrome. As i told before, if the users are offsite everything works as expected, Websites are blocked and show the blocking page.