-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
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
Cannot disable Shield if the URL host contains port #1896
Cannot disable Shield if the URL host contains port #1896
Comments
Is there a workaround for this? It's causing some trouble with a number of internal sites I have. Interestingly, I am able to disable shields on a site running on 8181, but any other port I see the same behavior as reported above. |
I ran into this same issue and your advice about port 8181 allowed me to work around it, so thanks! Remapping the host name and port to another name on port 8181 fixed it right up. I'm on Windows and I fixed it by:
Not the most elegant solution but it saves me from multiple browsers open at once. |
Still happening in:
I will keep this post up to date with the latest release candidate. |
Same here on MacOS, latest brave version. It's really annoying, because with this error + the CORS error (#2252), it's impossible for me to use brave to do web development :/ |
+1 |
Same issue, selecting |
i don't know about the 8080 port but yes on certain sites i cannot disable the shield. i can't disable it at all on those sires, not just disable and it reenables, on those site i can't switch it off at all. |
Would love for this to be fixed as I'm actively using Brave in web development using multiple local websites with different ports that need to interact. E.g. Angular and backend API. |
+1 I am also experiencing this.
Using a localhost setup and some things are simply not working correctly with Shield UP, and there is no way to turn them off. Tested the same exact sites works in Firefox, Chrome, and Edge, even with uBlock Origin, Privacy Badger, HTTPS Everywhere and Decentralized Eyes, the issue is specific to Brave. |
This bug is silently breaking various components of the web interface on millions of Network Attached Storage devices (e.g. Synology) and IPTV distribution systems (e.g. TVheadend). Specifically, it appears that HTTPS Everywhere is interfering with page rendering. Just wanted to document this and suggest the fix be deployed as soon as possible. |
That sounds like a new issue. |
In the online demo,* the Ad Control setting seems to be interfering too, and when it breaks, the page wont render at all, while HTTPS Everywhere disables parts of the page. But in either case, switching the Shield off entirely should resolve the issue, if that were possible. But there might be some caching I did not account for. |
Can you create a new issue with the label |
I dont think I can make labels because I dont have write access. And I am not sure how to properly characterize the issue yet: Does the global Shield control in the URL bar change any other hidden settings (besides the 5 toggles which you can see) ? |
Verification passed on
Used STR from the description. Verified passed with
Verification passed on
|
Got here because of the same problem. |
Is this fixed? |
@mcfaith9 issue should be fixed - QA has verified. Are you still encountering this problem? |
I'm following this issue for a while, and i lost track and forgot this. Yes its working fine now, Thank you! |
Description
The toggle button of the 'Shield' immediately switches back to 'Up' when trying to disable the Shield, if the URL in the address bar has some port in it.
Steps to Reproduce
Actual result:
Shield cannot not be disabled on URLs with port in its host.
Expected result:
Shield should be allowed to be disabled.
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
OS: MacOS mojave
Brave version: Version 0.55.20 Chromium: 70.0.3538.67 (Official Build) (64-bit)
and
OS: Arch Linux
Brave version: Version 0.55.10 Chromium: 70.0.3538.22 (Official Build)
Reproducible on current release:
Haven't tried yet.
Website problems only:
Additional Information
The text was updated successfully, but these errors were encountered: