-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore the googleadservices.com rule #865
Comments
Here's the full flow:
The destination server changes the request from:
to:
though that's not really important. |
The first thing I noticed in that flow is that that the The other thing I noticed is that several of these query strings are not encoded in "proper" HTML5 form format but we attempt to parse the query string nevertheless and fail to grab everything that's needed. Our currently available debouncing actions do not yet support the following hosts:
|
I took another look at the original Slack thread that caused us to remove the
*.googleadservices.com
debouncing rule.I believe that the initial rule that we removed was fine (
*.googleadservices.com
), though maybe it should have beenwww.googleadservices.com
. Removing that rule solved the initial breakage report we received, but covered up the two other broken rules involved in the redirect chain.These two rules were introduced in #726 and should be removed before we restore the
googleadservices.com
one:*.dartsearch.net
rule #867ad.doubleclick.net
rule #868The text was updated successfully, but these errors were encountered: