{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia7tk3ozdjl5pv46ty4liq56fhh7qzp72sjhnedtwh6notzc6rvme",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mir3bz2xttj2"
  },
  "path": "/viewtopic.php?t=32098&p=271881#p271881",
  "publishedAt": "2026-04-05T14:53:55.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://www.cloudflare.com/"
  ],
  "textContent": "> **back2themoon wrote :**\n> Hello again!\n> 1. When the HTTP Observer is enabled, and your Intercept & Modify HTTP Response extension is also installed (HTTP Observer=also enabled), is there some sort of overlap/clash issue or there's no problem?\n\nThe \"HTTP Observer\" in add-on \"Bypass Cloudflare with Backup Browser Cookies\" (the current name of this add-on - the 7.1 version) does not conflict with the \"HTTP Observer\" in add-on \"Intercept & Modify HTTP Response\" (the naming used in the two codes is different).\n\n\n> **back2themoon wrote :**\n> 2. Could you consider narrowing this extension's block to \"challenges.cloudflare.com\" only? It should be enough. I think its current block is a bit wider than that, possibly causing problems to some websites (mostly direct cloudflare.com ones)\n\nBlocking Cloudflare was only necessary when Cloudflare check blocked Pale Moon. That is no longer the case, so you should use the \"Unregister HTTP Observer\" add-on option. This will allow Cloudflare pages ( that do not use the check - such as https://www.cloudflare.com/ ) to load without issues in Pale Moon.\n\n**Screenshots:**\n\n\n> **back2themoon wrote :**\n> 3. Also, perhaps some internal clean-up to remove the old \"Bypass Cloudflare with Firefox Cookies\" strings? (including this thread title)\n> Also note the \"replace extension icon + Add-ons Manager icon\" tweaks (earlier in this topic) still work fine, but rely on the old \"Firefox\" naming.\n\nThe name \"Firefox\" no longer appears in the user interface, it only appears in the names of IDs, variables, functions, files, etc. within the add-on's code - where it appears 168 times (see the screenshot below). So I will not modify the add-on’s code, given the trade-off between the risk of introducing errors in code and the (non-existent) inconvenience caused to the user by keeping the \"Firefox\" strings in code. In fact, the user comes across the name \"Firefox\" but only in the CSS code within the \"userChrome.css\" file - for example, if he or she wants to change the add-on button icon. This interaction is a one-time action and does not require the user to inspect the CSS code (it only requires \"copy/paste\").\n\n**Screenshot:**\n\n\n* * *",
  "title": "Extension Releases/Support • Re: Bypass Cloudflare with Firefox Cookies",
  "updatedAt": "2026-04-05T14:53:55.000Z"
}