This repository was archived by the owner on Nov 15, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 15, 2017. It is now read-only.
HTTPs creates "extension errors" in other extensions (such as Adblock, Ghostery, TamperMonkey) #185
Description
I have noticed for a while now but just got around to writing you about it. Extension errors report that HTTPs is blocking access to about:blank and it always occurs with Adblock, Ghostery, and TamperMonkey (all except the last one are considered "privacy" extensions).
[Text for non-related issue moved to #186]
and the text of it beyond what you see in the picture is nothing more than a very long base64 encoding of an image (the red mesh that appears when a site is blocked) but just in case you need it here is the raw text for you.
Warning:
This extension failed to redirect a network request to about:blank because another extension (HTTP Switchboard) redirected it to data:text/html;base64,PCFET0NUWVBFIGh0bWw+IDxodG1sPiA8aGVhZD4gPHN0eWxlPiBAZm9udC1mYWNlIHsgZm9udC1mYW1pbHk6ICdodHRwc2InOyBmb250LXN0eWxlOiBub3JtYWw7IGZvbnQtd2VpZ2h0OiA0MDA7IHNyYzogbG9jYWwoJ2h0dHBzYicpLCB1cmwoJ2Nocm9tZS1leHRlbnNpb246Ly9tZ2hkcGVoZWpmZWtpY2ZqY2RiZm9maGNtbmpoZ2FhZy9jc3MvZm9udHMvUm9ib3RvX0NvbmRlbnNlZC9Sb2JvdG9Db25kZW5zZWQtUmVndWxhci50dGYnKSBmb3JtYXQoJ3RydWV0eXBlJyk7IH0gYm9keSB7IG1hcmdpbjogMDsgYm9yZGVyOiAwOyBwYWRkaW5nOiAwOyBmb250OiAxM3B4IGh0dHBzYixzYW5zLXNlcmlmOyB3aWR0aDogMTAwJTsgaGVpZ2h0OiAxMDAlOyBiYWNrZ3JvdW5kOiB0cmFuc3BhcmVudCB1cmwoJ2RhdGE6aW1hZ2UvcG5nO2Jhc2U2NCxpVkJPUncwS0dnb0FBQUFOU1VoRVVnQUFBQ01BQUFBakNBWUFBQUFlMmJOWkFBQUFCbUpMUjBRQS93RC9BUCtndmFlVEFBQUFDWEJJV1hNQUFBc1RBQUFMRXdFQW1wd1lBQUFBQjNSSlRVVUgzUWtPRmdjdmM0REVUd0FBQUJsMFJWaDBRMjl0YldWdWRBQkRjbVZoZEdWa0lIZHBkR2dnUjBsTlVGZUJEaGNBQUFDR1NVUkJWRmpEN1paQkNzQWdFQU1UNmYrL25KNWFyWWNxaUt0SVBBYUZZUjJERkNBQWdFUThpd3pMQ0x4WldnbFNaZ0tVZGdISmsya2RMRVk1QzRRQVV4ZUlGT0lOZndVT0JHa0xQQm5rQUlFRFFQb0VEaXcrdW9HSEJRNG92djRHbnZUTVM0RXZDK3d2aEJ2WUFsdGdDMnlCTGJBRlBsVGd2S0c2dnhYWkI2UU9sMlM3Z053Nmt0Z09wK0lIN3dBQUFBQkpSVTVFcmtKZ2dnPT0nKSByZXBlYXQ7IHRleHQtYWxpZ246IGNlbnRlcjsgfSBkaXYgeyBtYXJnaW46IDJweDsgYm9yZGVyOiAwOyBwYWRkaW5nOiAwIDJweDsgZGlzcGxheTogaW5saW5lLWJsb2NrOyBjb2xvcjogd2hpdGU7IGJhY2tncm91bmQ6ICNjMDA7IH0gPC9zdHlsZT4gPHRpdGxlPkJsb2NrZWQgYnkgSFRUUFNCPC90aXRsZT4gPC9oZWFkPiA8Ym9keSB0aXRsZT0nJmxkcXVvO3IuYWRzLnp5bmdhLmNvbSZyZHF1bzsgYmxvY2tlZCBieSBIVFRQIFN3aXRjaGJvYXJkJz4gPGRpdj5yLmFkcy56eW5nYS5jb208L2Rpdj4gPC9ib2R5PiA8L2h0bWw+.
ID: gighmmpiobklfepjocnamgkkbiglidom
Activity
gorhill commentedon Feb 6, 2014
Only one extension can redirect a request. The last one installed will have priority to redirect a request. So if you install Adblock after HTTPSB, you will find that Adblock creates "extension errors".
Ref.: webRequest: Conflict resolution
GuardianMajor commentedon Feb 6, 2014
Well this doesn't really address the problem. Even with the priority being given to the last extension, why is always
about:blankand why the inconsistent and weird behaviors of the about:blank and the apparent sticky behavior of the permissions of the last site being shown forabout:blank?I think you closed this a bit prematurely and without looking at my entire concern. The issue with the way
about:blankis being handled and its behavior remains.gorhill commentedon Feb 7, 2014
The issue is titled "HTTPs creates "extension errors" in other extensions (such as Adblock, Ghostery, TamperMonkey)", and my answer addresses this.
I rather have each opened issue focused on something specific, so that if a user comes here to look for a problem he is experiencing, he will be able to get a quick answer without wading long threads where answers to his issues are interleaved with other non-related issues. That the matrix of one page shows up onto another page is not related to "HTTPs creates "extension errors" in other extensions (such as Adblock, Ghostery, TamperMonkey)", and should have its own dedicated issue. I will open one for you: #186.
GuardianMajor commentedon Feb 7, 2014
Well I felt it did have relevance and was related given the redirect is to
about:blankand given that there are no permissions provided by the matrix for that and also it shows the permissions for the last page used would be relevant as the way it is handled might be the reason for the errors. But if you feel it merits its own topic, then ok.GuardianMajor commentedon Feb 7, 2014
Since the error clearly says that HTTPs is the one preventing the redirect to
about:blankhow is it that its not an issue with HTTPs, because we need to know WHY since that would be a behind-the-scene action which shouldn't be blocked based on my settings or its being blocked based on permissions which can't be set forabout:blankso how is the last extension installed can cause this a valid answer? Just wondering, since this is being explicitly laid at HTTPs feet by the system. I am trying to understand this behavior because it only happens with HTTPs enabled. Other extensions don't cause this without it.gorhill commentedon Feb 8, 2014
It's not about
about:blank, it's about HTTPSB issuing a redirect of its own choice of frame content replacement (data:text/html...), while ADB choose to replace the frame content with a redirect toabout:blank. But ADB redirect won't work because only one extension is allowed to redirect, and the last one wins -- as referenced above. See what happens if ADB is installed after HTTPSB:GuardianMajor commentedon Feb 8, 2014
Ok, I see what you mean. But still curious, can't we have HTTPs allow these redirects as part of the behind-the-scene scheme?
gorhill commentedon Feb 8, 2014
The redirect(s) will be reported on the matrix of the landing page if it is
http-based, otherwise HTTPSB doesn't support policing anything else than http-based network requests (i.e. nofile://,data://, etc.), because I don't see much benefit given the added work.