Administrators Marcos 5,074 Posted April 8, 2020 Administrators Share Posted April 8, 2020 That's normal. You should see one record for each file that is accessed, e.g css, js, html, etc. Link to comment Share on other sites More sharing options...
itman 1,659 Posted April 8, 2020 Share Posted April 8, 2020 5 minutes ago, Marcos said: That's normal. You should see one record for each file that is accessed, e.g css, js, html, etc. Ahh ......... Gotcha. I have to be careful with that trailing /* specification. Link to comment Share on other sites More sharing options...
Vojta 0 Posted June 7, 2020 Author Share Posted June 7, 2020 @Posolsvetla any update on this? Current release of https://web-board.budgetbakers.com causes the issue again. When I deploy the same release (the same Docker image) on another domain then it works fine. Link to comment Share on other sites More sharing options...
ESET Staff Posolsvetla 15 Posted June 7, 2020 ESET Staff Share Posted June 7, 2020 Unfortunately we are not able to provide any update on this issue yet. Link to comment Share on other sites More sharing options...
Vojta 0 Posted June 8, 2020 Author Share Posted June 8, 2020 I've attached diagnostics when trying to access our latest release. Is there anything that could help you solve the issue? Is there some workaround for our user other than completely disabling Web access protection? If I try Web access protection -> Url address management -> edit -> list of allowed addressess -> edit -> add "*.budgetbakers.com/*" and check "Notify when applying", then I see that URL was matched but the issue remains. What's the correct way to exclude our domain? Diagnostics.zip Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted June 8, 2020 Administrators Share Posted June 8, 2020 Adding the address to the list of allowed addresses cannot have any effect since it's not blacklisted by ESET. Instead try adding it to the list of addresses excluded from content scan. Link to comment Share on other sites More sharing options...
Vojta 0 Posted June 8, 2020 Author Share Posted June 8, 2020 Thanks it works. So what's next steps? How to fix it permanently without our users need to exclude our domain from checking? Should I report this issue somewhere else? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted June 8, 2020 Administrators Share Posted June 8, 2020 You can open a support ticket and refer to this topic so that the case is properly tracked. However, a developer of the web access protection has already replied you that we had no update on the issue yet. Link to comment Share on other sites More sharing options...
johnmorganhere 0 Posted June 11, 2020 Share Posted June 11, 2020 Hi everyone. I have never heard about it before. So as I understood it is some kind of an issue and it is not happened everytime? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted June 11, 2020 Administrators Share Posted June 11, 2020 7 minutes ago, johnmorganhere said: Hi everyone. I have never heard about it before. So as I understood it is some kind of an issue and it is not happened everytime? Do you regularly open / use the above website and have issues with it? Link to comment Share on other sites More sharing options...
Recommended Posts