Skip to content
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

'blip' in-browser JS ping utility (gfblip.appspot.com) doesn't work in Brave, does work in Chrome #12701

Open
gojomo opened this issue Nov 14, 2020 · 2 comments

Comments

@gojomo
Copy link

gojomo commented Nov 14, 2020

Description

Visiting @apenwarr's https://gfblip.appspot.com/ page, for a JS-based ping graph (source), works as expected in current MacOS Chrome (showing realistic ping times, indefinitely). But in current MacOS Brave (Version 1.16.76 Chromium: 86.0.4240.198 (Official Build) (x86_64)), it gives about 2 seconds of unrealistically-fast times (<10ms), then swiches to 100% max/red (>2000ms) results = until tab is reloaded.

Steps to Reproduce

  1. Visit https://gfblip.appspot.com/ in Brave

Actual result:

(while this screenshot is from just before updating, a full update showed the same behavior)

image

Expected result:

Here's how it looks in current Chrome (Version 86.0.4240.198 (Official Build) (x86_64)):

image

Reproduces how often:

Always

Brave version (brave://version info)

Brave 1.16.76 Chromium: 86.0.4240.198 (Official Build) (x86_64)
Revision d8a506935fc2273cfbac5e5b629d74917d9119c7-refs/branch-heads/4240@{#1431}
OS macOS Version 10.15.7 (Build 19H2)
JavaScript V8 8.6.395.25
Flash (Disabled)
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36
Command Line /Applications/Brave Browser.app/Contents/MacOS/Brave Browser --enable-dom-distiller --disable-domain-reliability --no-pings --extension-content-verification=enforce_strict --extensions-install-verification=enforce --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --sync-url=https://sync-v2.brave.com/v2 --lso-url=https://no-thanks.invalid --enable-features=MixedContentSiteSetting,AutoupgradeMixedContent,PassiveMixedContentWarning,WebUIDarkMode,PrefetchPrivacyChanges,PasswordImport,ReducedReferrerGranularity,LegacyTLSEnforced,OmniboxContextMenuShowFullUrls,DnsOverHttps --disable-features=PrivacySettingsRedesign,TextFragmentAnchor,AutofillEnableAccountWalletStorage,AllowPopupsDuringPageUnload,NotificationTriggers,SmsReceiver,TabHoverCards,VideoPlaybackQuality,AutofillServerCommunication,PasswordCheck,SafeBrowsingEnhancedProtection --flag-switches-begin --enable-experimental-web-platform-features --flag-switches-end
Executable Path /Applications/Brave Browser.app/Contents/MacOS/Brave Browser
Profile Path /Users/gojomo/Library/Application Support/BraveSoftware/Brave-Browser/Default

Version/Channel Information:

Haven't tried other channels.

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields?

No.

  • Does the issue resolve itself when disabling Brave Rewards?

Not enabled.

  • Is the issue reproducible on the latest version of Chrome?

No - works fine, per above.

@apenwarr
Copy link

apenwarr commented Nov 14, 2020 via email

@gojomo
Copy link
Author

gojomo commented Nov 19, 2020

Because of an oddity of how blip works, you have to visit it with an http URL, not https.

Thanks! Indeed, I can trigger a similar failure in Chrome now by choosing https.

But, there's no way to use http in Brave. All attempts are immediately redirecting to https. It looks like a "307 Internal Redirect" happening from the server "Google Frontend". But it aslo appears the Brave request included a "Upgrade-Insecure-Requests: 1" header. So I'm not sure if the cause is a Brave policy, a Google/Appspot policy, a choice in the Blip code, or an interaction of all of those.

Can I force Brave to load http://gfblip.appspot.com without triggering a redirect-to-https?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants