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
{{ message }}
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.
Currently, the extension pages still show as loading in the browser while it waits for the return from DNSLink. We should quickly return and not wait to avoid 4seconds of waiting (probably a 200 with a message saying this is reserved or that your extension isn't configured correctly).
The text was updated successfully, but these errors were encountered:
I am sort of doing this already for lume, and I plan on lume relays to handle this role which is a dummy node server that returns a status code defined in the request header. This thus solves the status code limitations firefox has in its webRequest API.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, the extension pages still show as loading in the browser while it waits for the return from DNSLink. We should quickly return and not wait to avoid 4seconds of waiting (probably a 200 with a message saying this is reserved or that your extension isn't configured correctly).
The text was updated successfully, but these errors were encountered: