poiriern1

Planet thank you for your post here, you've helped me finally realize the issue that has stumped me for over a week or so. We've been using 6.0.24.0 on Mac OS X Yosemite and recently migrated our entire ESET environment to version 6. We use ERA to deploy policies, configurations, tasks, etc. and I was constantly making updates to Protocol Scanner settings, allowed exceptions, excluded from checks, Web Access Protection settings, you name it and the problem still occurred, we experienced the same issue where CSS and JS files were not being retrieved, same error you mentioned above in Safari only, doesn't seem to be an issue with any other browser. The odd thing here is we are able to hit the site successfully using hxxp://domain.comand HTTPS://domain.com but when we just enter domain.com the issue occurs. So like you said, certainly the protocol scanner would be the culprit. I even tried downgrading to 6.0.18.1 and the problem still occurs, when you first install ESET and it is up and running the problem does NOT occur, but if you restart the machine then the problem occurs. Hopefully ESET can pull something together for this bug here.