You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MDN doc about the firefox's proxy API, it's quite different from chromium's chrome.proxy.
use browser.proxy.onRequest.addListener(listener, {urls:['<all_urls>']}) to get requestDetail.
usually, the requestDetail.documentUrl of extension request is in format like: moz-extension://${internalUUID}/path listener returns an invalid proxy to block request 🤣
internalUUID is unique for each extension, but it's different from the extension id returned by browser.management.getAll(), and I can't find a way to get it in extension.
one way to get internalUUID is, open this page about:debugging#/runtime/this-firefox, run some snippet in devtool:
Hey that's great! I tried proxy.onRequest in chrome a while ago, and yes, didn't show extension traffic, nice find for firefox!
Thanks for the pointer, I'll try digging into it as well.
Could I please request that Firefox (specifically Zen Browser, which is basically Firefox) is looked at again as a new home/continuation for Little Rat? I must say, without Little Rat I feel like most extensions are not worth using. Thanks for your hard work.
TLDR: use
browser.proxy.onRequest
.MDN doc about the firefox's proxy API, it's quite different from chromium's
chrome.proxy
.use
browser.proxy.onRequest.addListener(listener, {urls:['<all_urls>']})
to getrequestDetail
.usually, the
requestDetail.documentUrl
of extension request is in format like:moz-extension://${internalUUID}/path
listener
returns an invalid proxy to block request 🤣internalUUID
is unique for each extension, but it's different from the extension id returned bybrowser.management.getAll()
, and I can't find a way to get it in extension.one way to get
internalUUID
is, open this pageabout:debugging#/runtime/this-firefox
, run some snippet in devtool:related issues: #8, #14
The text was updated successfully, but these errors were encountered: