Disable CORS in Brave Browser - brave

Recently I've switched from Safari to Brave (Safari has a horrible bug - when ever you open dev tools, you get logged out from every site), and I'm trying to run it in CORS disabled mode.
I've tried modifying the command I would usually use for Chrome, but every attempt was unsuccessful:
open /Applications/Google\ Chrome.app --args --user-data-dir="/var/tmp/Chrome dev session" --disable-web-security
My local Angular app is connecting to couple of remote servers and all requests get blocked unless I disable CORS - and no I can't make any changes on the servers.

here is what work for me, I use OSX this way you don't need to close other opened brave apps.
open -n -a /Applications/Brave\ Browser.app/Contents/MacOS/Brave\ Browser --args --user-data-dir="/tmp/brave_dev_sess_1" --disable-web-security

Because Brave is a version of the Chromium Web Browser, the same methods that work for Chrome will work for Brave. See the post: Disable same origin policy in Chrome
The answer that specifically worked for me was Windows + r
brave.exe --user-data-dir="C://Chrome dev session" --disable-web-security "enter url here"

Related

How to stop Firefox debugger server without restarting Firefox

I have a VSCode config that will start the Firefox debugger server with -start-debugger-server, so that I can run an npm script and launch a website in my existing firefox windows without having to run a special firefox window with the debug server enabled.
Is there a way to turn the debugger server off short of re-starting Firefox? Something like a -stop-debugger-server CLI argument would be nice but there doesn't appear to be such a flag.
I've tried -stop-debugger-server, tried looking in the firefox CLI wiki, tried a web search. Stopped short of trying to re-start Firefox from the command line

Starting Chrome on macOS from the Finder with extra command line parameters

I want to stuff remote debugging and other esoteric dev-only only parameters to the Chrome application when it starts but I want it to be always there, including when I click on the app icon.
E.g.:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
How do I pass these command line parameters to the app directly?
I ended up creating an automator application with as shell task. Customized the icon and replaced Chrome.app with the new app in the dock.
I am still looking for a way to change the settings in Chrome so it can connect with remote debugger "on-demand" for specific tasks (not everything as it is set now) but that doesn't seem to be possible at this time. The VSCode folks have apparently solicited the Chrome team to provide this functionality. Stay tuned...

Javascript console not working if Google Chrome is started from OS X terminal

Since I am working locally with d3.js, I need to launch Google Chrome with the --allow-file-access-from-files option. To do this, I start Chrome from the OS X terminal, as follows:
open /Applications/Google\ Chrome.app --args --allow-file-access-from-files
However, it seems that this prevents the javascript console from working correctly. console.log() does not print anything anymore. I suppose the output is redirected elsewhere when Chrome is started this way.
Is there a way to launch Chrome with options and still have the console working as usual?
I've got the same problem. The solution for me was to uncheck the "Set locale environment variables on startup" checkbox in the terminal settings.
After that, restart the terminal and google chrome.
https://groups.google.com/forum/#!topic/google-chrome-developer-tools/rC9_0sIejvs

Google developer console not loading in Chromium on Debian 7

I am using Debian 7 and Chromium browser.
I'm setting up OAuth authentication via google developer console, but for some reason when I enter https://console.developers.google.com, browser starts loading the page, saying "Waiting for console.developers.google.com" and is stuck forever.
Once in ~7 times it eventually loads the page, but then when I click on any tab, it freezes again.
Anyone experienced something like that?
P.S. On Windows everything's fine.
P.P.S The problem is specific for Chromium browser. Chromium also glitches with google+ notifications - they won't load.
you can try loading Google developer console in privacy mode, meaning opening the console from https://cloud.google.com/ in an incognito window.
"If it works there, it means one of your extensions is causing the security problem and you should remove it." as it explained on the Google Chome Help page :'Fix connection errors.' (Your connection is not private > Tip 2: Try opening the page in incognito mode.)

SinchPSTNsample Using javascript Shows Warning After running index.html file

i saw below warnning when running the sample html in chrome
Warning! Protocol "file" used to load page in Chrome.
Please avoid loading files directly from disk when developing WebRTC applications using Chrome.
Chrome disables access to microphone which prevents proper functionality.
You can allow working with "file:", if you start Chrome with the flag --allow-file-access-from-files
Please help me to get out of this
thank you
It depends on which Operating System.
In OS X you can start Chrome by using:
open -a Google\ Chrome --args --allow-file-access-from-files
While in Windows you'd start Chrome in the command prompt using:
chrome.exe --allow-file-access-from-files
Please note that the warning does not disappear in the sample app, this is the expected behaviour but now calls will work. In a production environment you should not even include this warning, since it's only meant as a friendly reminder for developers using local file storage (directly opening the .html file from disk).

Resources