You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure how long the issue has been present because we primarily use Firefox and Google Search. The issue only came to light recently with a user that uses Edge and thus Bing search.
To replicate, open Microsoft Edge and load bing.com website. Then type in something such as this - relaxing music for children.
It will load that page, then when you click on any of the videos, it will be blocked by the content filter with a score of around 400! The only way to fix the issue is to add bing.com/videos to exceptionurllist to bypass the content filter which means none of the videos in Bing are filtered in any way.
Google Search:
I have also noticed over the years, that Google Search, Google Docs and Google Mail also shows up a lot of denied content filter messages. However it never seemed to affect search results and no user has ever reported any issues with using any of the Google Websites.
I believe the content filter issue is more related to a Javascript function (at least for Google Search) that causes the content filter to be around 180 - https://www.google.co.uk/xjs/ gives DENIED Content Check limit of 160 : 182 and Proxy, Hacking, Weapons, Pornography
Other than creating loads of DENIED messages in the logs, it doesn't seem to cause any issues with any Google sites such as Search, Maps, Docs, Gmail etc. However, I don't know if it affects performance of Google websites as a result of this blocking? Would it be possible to review this, so that E2guardian provides a recommendation on how to deal with this. Should it be blocked (whatever is actually being blocked - I assume a javascript of some sort) or should E2guardian default to allowing this, without compromising content and search term filtering. If it should be blocked would it be possible for E2guardian to default to not logging this block if the error message is one that should simply be ignored as noise in the logs.
Restarting E2guardian:
Just a small point and not really an issue. When restarting E2guardian, I notice dropped connections in the Iptables Firewall Log.
IN= OUT=lo SRC Proxy Server IP DST Proxy Server IP DPT 8081 and repeated for ports 8082 to 8085. I never see this in the logs when the actual Server is restarted although it's possible that E2guardian starts before the Firewall starts when booting up? Not an issue, but just thought I would mention it, as it's unexpected. I only have IP Address 127.0.0.1 allowed for local loopback, not the IP address allocated to E2guardian.
My main concern is Bing Videos and Google Content Filter issues.
The text was updated successfully, but these errors were encountered:
Update on the google.co.uk/xjs issue. The content score for this is 172. If the naughtyness filter is below this, then google Search does not work properly. When you press enter, it goes to a new line in the search results instead of loading search terms.
So I have had to add google.co.uk/xjs to the exceptionurllist so that we can filter Google Searches whilst still allowing Google Search to work correctly.
Given that pretty much everyone uses Google Search and that E2guardian needs to filter Search Results, I would recommend that E2guardian is updated to address this issue with Google. Whilst not technically a bug, Google Search is broken when trying to implement standard filtering.
Bing Videos:
Not sure how long the issue has been present because we primarily use Firefox and Google Search. The issue only came to light recently with a user that uses Edge and thus Bing search.
To replicate, open Microsoft Edge and load bing.com website. Then type in something such as this - relaxing music for children.
It will load that page, then when you click on any of the videos, it will be blocked by the content filter with a score of around 400! The only way to fix the issue is to add bing.com/videos to exceptionurllist to bypass the content filter which means none of the videos in Bing are filtered in any way.
Google Search:
I have also noticed over the years, that Google Search, Google Docs and Google Mail also shows up a lot of denied content filter messages. However it never seemed to affect search results and no user has ever reported any issues with using any of the Google Websites.
I believe the content filter issue is more related to a Javascript function (at least for Google Search) that causes the content filter to be around 180 -
https://www.google.co.uk/xjs/ gives DENIED Content Check limit of 160 : 182 and Proxy, Hacking, Weapons, Pornography
Other than creating loads of DENIED messages in the logs, it doesn't seem to cause any issues with any Google sites such as Search, Maps, Docs, Gmail etc. However, I don't know if it affects performance of Google websites as a result of this blocking? Would it be possible to review this, so that E2guardian provides a recommendation on how to deal with this. Should it be blocked (whatever is actually being blocked - I assume a javascript of some sort) or should E2guardian default to allowing this, without compromising content and search term filtering. If it should be blocked would it be possible for E2guardian to default to not logging this block if the error message is one that should simply be ignored as noise in the logs.
Restarting E2guardian:
Just a small point and not really an issue. When restarting E2guardian, I notice dropped connections in the Iptables Firewall Log.
IN= OUT=lo SRC Proxy Server IP DST Proxy Server IP DPT 8081 and repeated for ports 8082 to 8085. I never see this in the logs when the actual Server is restarted although it's possible that E2guardian starts before the Firewall starts when booting up? Not an issue, but just thought I would mention it, as it's unexpected. I only have IP Address 127.0.0.1 allowed for local loopback, not the IP address allocated to E2guardian.
My main concern is Bing Videos and Google Content Filter issues.
The text was updated successfully, but these errors were encountered: