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

Web site throwing "Culture is not supported" error and stops working #24564

Closed
aseedig opened this issue Aug 10, 2022 · 9 comments
Closed

Web site throwing "Culture is not supported" error and stops working #24564

aseedig opened this issue Aug 10, 2022 · 9 comments
Assignees
Labels

Comments

@aseedig
Copy link

aseedig commented Aug 10, 2022

Description

When working on an analytics dashboard website and try to export data to excel, the server responds with the following error:
"There was an error while processing your request.
The error was: Culture is not supported. Parameter name: name en-GB;q=0.8 is an invalid culture identifier."

It seems that the Language settings is adding the following parameters to the Request Header: "name en-GB;q=0.8"
This was working in previous Brave versions and I discovered this issue since Brave Version v1.42.86

Steps to Reproduce

You would need access to the application to reproduce the issue. However, the Request Header contains the above mentioned parameter and this needs to be addressed. I might be able to grant access to an export function for trouble shooting purposes, but cannot give access here to the restricted internal application. This export function is working with:

  • Chrome Version 104.0.5112.79 (Official Build) (x86_64)
  • MS Edge: Version 104.0.1293.47 (Official build) (x86_64)

Actual result:

image

Expected result:

image

Reproduces how often:

Easily reproducible... Just need access to the export function.

Brave version (brave://version info)

Brave 1.42.88 Chromium: 104.0.5112.81 (Official Build) (x86_64)
Revision 5b7b76419d50f583022568b6764b630f6ddc9208-refs/branch-heads/5112@{#1309}
OS macOS Version 12.5 (Build 21G72)
JavaScript V8 10.4.132.20
User agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.81 Safari/537.36
Command Line /Applications/Brave Browser.app/Contents/MacOS/Brave Browser --disable-domain-reliability --enable-dom-distiller --component-updater=url-source=https://go-updater.brave.com/extensions --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --sync-url=https://sync-v2.brave.com/v2 --lso-url=https://no-thanks.invalid --variations-server-url=https://variations.brave.com/seed --variations-insecure-server-url=https://variations.brave.com/seed --enable-features --disable-features --flag-switches-begin --flag-switches-end
Executable Path /Applications/Brave Browser.app/Contents/MacOS/Brave Browser
Profile Path /Users/aseedig/Library/Application Support/BraveSoftware/Brave-Browser/Default
Linker lld
Active variations AdRewardsStudy:NextPaymentDay
BraveAds.AdServingStudy:DefaultAdNotificationsPerHour=10/MaximumAdNotificationsPerDay=100/MaximumInlineContentAdsPerHour=12/MaximumInlineContentAdsPerDay=60/AdServingVersion=1
BraveAds.EpsilonGreedyBanditStudy:Default
BraveAds.FrequencyCappingStudy:ExcludeAdIfWithinTimeWindow=0h
BraveAds.UserActivityStudy:Triggers=NTPSI/TimeWindow=15m/Threshold=0.0/IdleTimeThreshold=5s
BraveDebounceStudy:Enabled
ConversionsStudy:NewDefaultPattern
Default1pBlockingStudy:Disabled
DisableReduceLanguage:Enabled
EphemeralStorageStudy:Enabled
ExtendedVariationsSafeMode5:SignalAndWriteViaFileUtil5
FirstPartyEphemeralDomainBlockStudy:Enabled
ForceDisableBlinkFeatures:Enabled
MacCoreLocationBackendStudy:Enabled
PartitionBlinkMemoryCacheStudy:Enabled
PartitionConnectionsByNetworkIsolationKeyStudy:Enabled
PermissionLifetimeReleaseStudy:Enabled
RequestAdsEnabledApiStudy:Enabled
SpeedreaderReleaseStudy:Enabled

Version/Channel Information:

I only tested it with the current Official Build.

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields? Yes.
  • Does the issue resolve itself when disabling Brave Rewards? No.
  • Is the issue reproducible on the latest version of Chrome? No.

Miscellaneous Information:

@rebron
Copy link
Collaborator

rebron commented Aug 12, 2022

@aseedig Do you have a pointer to the website/app where you're seeing this error?

@rebron rebron added the needs-more-info The report requires more detail before we can decide what to do with this issue. label Aug 12, 2022
@rebron rebron added feature/shields/fingerprint The fingerprinting (aka: "device recognition") protection provided in Shields workaround/shields-down labels Aug 12, 2022
@aseedig
Copy link
Author

aseedig commented Aug 12, 2022

Not yet, but can produce something shortly. As mentioned, this is an internal analytics dashboard of an insurance company and I cannot share the data in the public. I can however make a test page accessible for testing and reproduction. Just wanted to know that someone is picking it up.

@pilgrim-brave
Copy link

Please and thank you.

@aseedig
Copy link
Author

aseedig commented Aug 12, 2022

Hey guys,

please us the following URL for testing:
https://manager.hampshire4x4response.net/Application/rdPage.aspx?rdReport=ExportTest

Please let me know if you need anything else.

I have set the debug mode to on, so you will see a lot of details in the data. but nothing points to the error apart the message that the Culture is not supported:
[Culture is not supported. Parameter name: name en-GB;q=0.9 is an invalid culture identifier.]

Disable Shields Up and the export works.

Thanks

Axel

@pilgrim-brave
Copy link

Thank you. I confirmed the bug and also confirmed that it is fixed already in nightly builds by brave/brave-core#14338.

@pilgrim-brave
Copy link

Thanks very much for the bug report. As I mentioned, it's fixed in nightly and so will be made available on all platforms shortly, in version 1.44. In the meantime, you can work around it by going into the shields panel, under Advanced Controls, change "Block fingerprinting" to "Allow fingerprinting" for this site. (You don't need to disable "Shields Up" entirely.)

Thank you very much for taking the time to report the bug and helping us get this sorted; it's greatly appreciated. I am checking if there is anything i can do to get to fix shipped faster, but worst case know it'll be in version 1.44.

@aseedig
Copy link
Author

aseedig commented Aug 15, 2022

Great news. Thank you for taking this on and resolve it so quickly.
Great work.

Axel

@rebron rebron added this to the 1.44.x - Beta milestone Aug 30, 2022
@rebron rebron added QA/Yes release-notes/include and removed needs-more-info The report requires more detail before we can decide what to do with this issue. labels Aug 30, 2022
@stephendonner stephendonner added the QA/In-Progress Indicates that QA is currently in progress for that particular issue label Sep 14, 2022
@stephendonner
Copy link

stephendonner commented Sep 15, 2022

Verified PASSED using

Brave 1.44.82 Chromium: 105.0.5195.102 (Official Build) beta (x86_64)
Revision 4c16f5ffcc2da70ee2600d5db77bed423ac03a5a-refs/branch-heads/5195_55@{#4}
OS macOS Version 13.0 (Build 22A5342f)

NOTE: could not reproduce the issue as filed using 1.43.89 Chromium: 105.0.5195.102

Steps:

  1. installed 1.44.82
  2. launched Brave
  3. ensured Prevent sites from fingerprinting me in brave://settings/shields`
  4. loaded https://manager.hampshire4x4response.net/Application/rdPage.aspx?rdReport=ExportTest

Confirmed I was able to load and export the data without issue/exceptions in the JavaScript Console panel

example example example example
Screenshot 2022-09-14 at 5 28 37 PM Screenshot 2022-09-14 at 5 28 41 PM Screenshot 2022-09-14 at 5 28 51 PM Screenshot 2022-09-14 at 5 30 58 PM

@stephendonner stephendonner added QA Pass-macOS and removed QA/In-Progress Indicates that QA is currently in progress for that particular issue labels Sep 15, 2022
@aseedig
Copy link
Author

aseedig commented Sep 15, 2022 via email

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

No branches or pull requests

4 participants