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
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Some rules breaks third party sites, see e.g. #4510 or #4545.
I'm not happy with the idea of disabling such rules completely since many other sites depends on them and are working fine.
How can we handle this growing issue?
The Google Videos ruleset was disabled when it was found to be causing problems. Why not disable the rules when they cause problems, and only re-enable them once the problem has been solved? I don't know about you, but I value a site's functionality more than HTTPS for every single possible element.
I'm generally in favor of the approach described by @terrorist96 as well.
With the larger sites, it's likely we can find someone on their security teams that could maintain these rulesets for us, which would probably be a more streamlined process. Then we could open any issues directly with them, rather than these issues percolating to the major ruleset maintainers.
With the smaller sites with broken rulesets, it won't be a big deal if we disable them completely for a while until someone comes along and fixes them.
Activity
J0WI commentedon Jul 12, 2016
In some cases this is related with #49
terrorist96 commentedon Jul 13, 2016
The
Google Videosruleset was disabled when it was found to be causing problems. Why not disable the rules when they cause problems, and only re-enable them once the problem has been solved? I don't know about you, but I value a site's functionality more than HTTPS for every single possible element.Hainish commentedon Jul 27, 2016
I'm generally in favor of the approach described by @terrorist96 as well.
With the larger sites, it's likely we can find someone on their security teams that could maintain these rulesets for us, which would probably be a more streamlined process. Then we could open any issues directly with them, rather than these issues percolating to the major ruleset maintainers.
With the smaller sites with broken rulesets, it won't be a big deal if we disable them completely for a while until someone comes along and fixes them.
Hainish commentedon Oct 13, 2016
Some of this discussion has continued in #7338
gloomy-ghost commentedon Apr 28, 2018
#15157 solves a big proportion of issues caused by CDN rules (if not all of them), should this be closed?
Hainish commentedon Jul 6, 2018
@gloomy-ghost yes, thanks.