A new extra header to control access to private networks has been introduced. Access-Control-Allow-Private-Network: true
.
But...
May 2022: Chrome 102 rolls out to Stable. The deprecation trial ends. Chrome blocks all private network requests from public, non-secure contexts.
It's not clear to me if "Access-Control-Allow-Private-Network: true" will bypass this limitation.
So Snap! should be served from HTTPS URL (secure context) with "mixed content" enabled.
And/Or ESP32/PICO board with the local server running HTTPS endpoint should be used.
It's a browser setting or command line switch - it changes every few months ;(
Starting the fresh one, not shared, Chrome process with the "--allow-running-insecure-content --disable-web-security" should do the trick.
To enforce the new process, kill the other instances of Chrome, or use the switch
"--user-data-dir=\some_directory"
"--profile-directory=\other_directory"