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

Possible false positive with Adobe Test & Target rule (Facebook CDN) #560

Open
steveluscher opened this issue May 30, 2020 · 2 comments
Open

Comments

@steveluscher
Copy link

@steveluscher steveluscher commented May 30, 2020

Description

I have received a report of Ghostery blocking this resource. The block was made according to the ‘Adobe Test & Target’ rule:

https://static.xx.fbcdn.net/rsrc.php/v3/yM/r/MBOX6JqmhhS.js?_nc_x=yIsXPYraEd4

This is a resource from the Facebook CDN that, like many others like it, is critical for the operation of the website. Do you see anything about that file or that URL that would trigger that rule, and do you believe this to be a false positive that can be fixed?

Expected Behavior

Resource should trigger no rule.

Actual Behavior

Resource triggers the ‘Adobe Test & Target’ rule; gets blocked.

Steps to Reproduce

  1. Use Ghostery.
  2. Load the Beta version of facebook.com.
  3. Observe that https://static.xx.fbcdn.net/rsrc.php/v3/yM/r/MBOX6JqmhhS.js?_nc_x=yIsXPYraEd4 triggers the ‘Adobe Test & Target’ rule; gets blocked.
@christophertino
Copy link
Member

@christophertino christophertino commented Jun 26, 2020

This looks like a false positive. Adobe Target uses something called mbox which we are catching in your Facebook CDN pattern. I'll get this cleaned up on our end. Thanks for reporting.

@christophertino christophertino self-assigned this Jun 26, 2020
@steveluscher
Copy link
Author

@steveluscher steveluscher commented Jun 27, 2020

That's great news; thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants