We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The latest Brave browser has issues with https://ipv4.icanhazip.com/
Version 1.75.175 Chromium: 133.0.6943.54 (Official Build) (64-bit)](https://brave.com/latest/)
Brave treats https://ipv4.icanhazip.com/ as triggering an AD BLOCK response
This results in a (blocked:other) or ERR_BLOCKED_BY_CLIENT response.
(blocked:other)
ERR_BLOCKED_BY_CLIENT
This leaves is-online limping on one leg to determine online status.
My suggestion is to allow the user to pass in alternative fallbacks so if ERR_BLOCKED_BY_CLIENT happens it can have some other options to try
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The latest Brave browser has issues with https://ipv4.icanhazip.com/
Version 1.75.175 Chromium: 133.0.6943.54 (Official Build) (64-bit)](https://brave.com/latest/)
Brave treats https://ipv4.icanhazip.com/ as triggering an AD BLOCK response
This results in a
(blocked:other)
orERR_BLOCKED_BY_CLIENT
response.This leaves is-online limping on one leg to determine online status.
My suggestion is to allow the user to pass in alternative fallbacks so if
ERR_BLOCKED_BY_CLIENT
happens it can have some other options to tryThe text was updated successfully, but these errors were encountered: