4 ms·
> Starting with Chrome 94, Chrome no longer allows HTTP requests to local IP addresses. Since Portal worked by accessing a local server running on your phone to
by seanwilson 5y ago
> Starting with Chrome 94, Chrome no longer allows HTTP requests to local IP addresses. Since Portal worked by accessing a local server running on your phone to do all file transfers locally over WiFi, this means Portal no longer works for anyone using Chrome. Since Chrome and Chromium variants have overwhelming browser dominance, this means Portal will soon no longer work for the vast majority of people.
The linked post (https://developer.chrome.com/blog/private-network-access-update/#accessing-localhost https://developer.chrome.com/blog/private-network-access-upd...) says "If your website needs to issue requests to localhost, then you just need to upgrade your website to HTTPS". Also, I just tested a Chrome extension on Chrome 94 and it has no problem sending a fetch API request to http://localhost http://localhost so maybe that's an option too?
Am I missing something?
- kevingadd 5y ago"local ip address", not localhost. They're doing file sharing on the local network. This also means that the common 'install a custom root for localhost' https trick won't work because it's machine-to-machine communication - https everywhere specifically stops machines from communicating locally. You could probably hack it with a relay server but at that point, why bother?