WebVue and uBlock origin

7 Posts
5 Users
0 Likes
54 Views
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
Topic starter
 

Hello,
A quick experience sharing: I am using a AD Blocker named uBlock origin and realized WebVue is not working correctly.
Effect: The home page is never displayed.
Why: The filter used by this blocker is detecting a "Bad string" in one of the url script uploaded to the browser.
The guilty url:

unluckily, uBlock is detecting the string "/log/views/" therefore it is blocking the page!

Other Blockers could have the same behavior, take care...

Nico

 
Posted : 09/11/2022 1:20 am
KASI
 KASI
(@k-simanjalamarcinfo-com)
Posts: 134
Estimable Member
 

Thank you for the sharing Nico. I have already encounter issue with this extension, so my work around is temporarily to disable the extension only for the WebVue website. I will do this each time I redeploy WebVue with different IP or hostname. Did you find a better way or any method we can make exclusion for the /logs/views syntax?

Thanks,
Kantha

 
Posted : 09/11/2022 9:34 am
b.lepeuple
(@b-lepeuplearcinfo-com)
Posts: 149
Estimable Member
 

Hi,
One way might be to get in touch with the publisher of the extension so that he changes the rule he has.
We do that on a regular basis with antivirus publishers when our products trigger false positive (happens with free software that are largely based on very generic rules).
Regards

 
Posted : 09/11/2022 2:23 pm
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
Topic starter
 

Hi,

To Kantha: Yes, I did the same, just add the website url as an exception for the blocker
To Benoit: Hmmm, it looks difficult to ask this guy to remove the filter for all the world because WebVue is impacted 🙂
Why not changing our url ?

Nico

 
Posted : 09/11/2022 4:40 pm
b.lepeuple
(@b-lepeuplearcinfo-com)
Posts: 149
Estimable Member
 

"Why not changing our Url ?" --> Because, unless I miss something, there is nothing wrong in it. It is not a piece of code that is what that extension is designed to block.
And I have not said "ask them to remove the rule".
They have probably implemented a very wide catching rule, there is nothing wrong in letting them know that it triggers false positive and that it would be good if they could have an eye on it to reduce its catching surface.

 
Posted : 10/11/2022 2:24 pm
f.martin
(@f-martinarcinfo-com)
Posts: 148
Member Admin
 

A little follow-up due to recent messages on Teams

We had a short discussion with Nicolas 2 months ago and, as we guessed, we found that there is rule matching one of our internal url.

The corresponding rule is in this file (at least): https://easylist.to/easylist/easyprivacy.txt
And it block any url containing "/log/views/"

Two solutions:
- Add WebVue in the Whitelist menu of uBO
- Add "*/log/views/*" in the Whitelist menu of uBO

ref: https://github.com/gorhill/uBlock/wiki/How-to-mark-a-web-site-as-trusted#specific-pattern

 
Posted : 12/01/2023 12:11 am
LM
 LM
(@l-micaudarcinfo-com)
Posts: 383
Member Admin
 

Thank you for the report.

For the moment it works on my side with this filter in uBlock:

@@||*/GraphicalData/js/jsHMI/sv/viewers/log/views/*$script

 
Posted : 12/01/2023 4:07 am