404 Error When .Well Know Not Found

[dknopf]

I'm not sure if this is intended or not, but on any site that doesn't have a .well-known/gpc.json file there is a 404 error. This happens even when the extension is disabled via the popup disable button.

[SebastianZimmeck]

Good point, @dknopf. I believe I mentioned that a while back to @kalicki1 and we settled on being OK with those 404s. (There is essentially no way around those, as I see it.)

[dknopf]

Yeah I figured you guys had seen it, I was just wondering if there was some way of suppressing the error and instead printing out a message or something, just so that other developers don't think there's a problem in our code.

[kalicki1]

So I just took a look at the error, and yes I agree with @SebastianZimmeck that the 404s are probably alright. I would hope developers would be able to see the 404 is on the 1st party's hands for missing a .well-known, not ours. I think the more concerning thing was that the extension would continue to send content scripts regardless of whether OptMeowt was enabled or not. I'm pushing a change that will turn off contentScript.js when the extension is disabled, which shuts off all action on a page for good.

[SebastianZimmeck]

Maybe, add a sentence to the readme that not finding a .well-known will cause a 404 error.