Skip to content
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

Chrome Extension does not handle all requests #1348

Closed
BlazDT opened this issue Mar 23, 2019 · 10 comments

Comments

Projects
None yet
3 participants
@BlazDT
Copy link

commented Mar 23, 2019

Visit this site while Chrome Extension is showing filter protocol:
https://static.crunchyroll.com/vilos/player.html

No requests are shown. When doing the same with FireFox it works fine.
This issue results in ads getting played on crunchyroll.com with US IP.

AdguardTeam/AdguardFilters#29942

@ameshkov ameshkov added this to the 3.1 milestone Mar 23, 2019

@maximtop

This comment has been minimized.

Copy link
Contributor

commented Mar 25, 2019

Somehow requests do not trigger event listeners in the browser.webRequest api after the site is cached.
After clearing cache, request events appear for 1-2 page reloads and then disappear again.
Seems like this is an chrome bug.

@BlazDT

This comment has been minimized.

Copy link
Author

commented Mar 27, 2019

Is there a ticket number at Google yet?

@ameshkov

This comment has been minimized.

Copy link
Member

commented Mar 28, 2019

Guys, could it be that this request is cached by a service worker?

@maximtop

This comment has been minimized.

Copy link
Contributor

commented Mar 28, 2019

I didn't find there any service workers
It is application cache
https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache

@BlazDT

This comment has been minimized.

Copy link
Author

commented Apr 3, 2019

So we are waiting for Google to fix it?

@ameshkov

This comment has been minimized.

Copy link
Member

commented Apr 3, 2019

Yes, and we need to file a bug report to them.

@maximtop

This comment has been minimized.

Copy link
Contributor

commented Apr 15, 2019

@ameshkov ameshkov removed this from the 3.1 milestone Apr 15, 2019

@maximtop

This comment has been minimized.

Copy link
Contributor

commented Apr 18, 2019

I'm closing this issue because chrome developers won't fix this bug.
https://bugs.chromium.org/p/chromium/issues/detail?id=952882#c5

@maximtop maximtop closed this Apr 18, 2019

@BlazDT

This comment has been minimized.

Copy link
Author

commented Apr 18, 2019

Great google :(

@ameshkov

This comment has been minimized.

Copy link
Member

commented Apr 20, 2019

As usual

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.