Hacker News Reader

Comment by urbandw311er | Hacker News Reader

Constantly errors by triggering cross-origin / access control checks in browser: is this intended and is the tool still effective in spite of this?

View on HN

The preflight requests themselves consume a small amount of bandwidth, so at scale I guess it could work?

Thank you for feedback! In order to work effectively vs some sites, you may need to run Chrome with CORS disabled: https://alfilatov.com/posts/run-chrome-without-cors/

Windows: Right click on desktop, add new shortcut, Add the target as "[PATH_TO_CHROME]\chrome.exe" --disable-web-security --disable-gpu --user-data-dir=~/chromeTemp , Click OK.

OSX: open -n -a /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --args --user-data-dir="/tmp/chrome_dev_test" --disable-web-security Linux: google-chrome --disable-web-security

No. What you clearly teaching is utmost harmful for the security. Are you going to be responsible if someone lose money from their bank account? And please don't expect all hackernews reader to understand the meaning of cors. Not all of us are fronted developer right?

The best way is to create some node or binaries (rust/go/c++) and run them.

https://pastebin.com/preUNcNR

I wonder why Chrome even has such setting, like what's the use case for it?

When you do local web developement, I enabled it for example.

But of course never browse the web with this instance of disabled security.

Does CORS security work on the client side response data? The server should still receive the load, right?

Reply on news.ycombinator.com