This MV3 implementation is interesting, but I’m curious how the extension handles the API request signing required by Pi-hole v6 to ensure requests originate from your specific client. Does the extension store the client token locally, or does it rely on the browser’s built-in CORS handling for the v6 endpoint?
This MV3 implementation is interesting, but I’m curious how the extension handles the API request signing required by Pi-hole v6 to ensure requests originate from your specific client. Does the extension store the client token locally, or does it rely on the browser’s built-in CORS handling for the v6 endpoint?