-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Safari CORS problem #3154
Comments
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
https://www.chromestatus.com/feature/4539473312350208 i think this could be the problem, bcos i find that the api in the browser would generate a "same-origin" header... this obviously won't allow a webapp deployed on https to connect a local machine http://localhost:5001 |
Does this happen against js-ipfs too? |
just tried shooting up jsipfs daemon... same problem for Safari + Https... |
@lidel is this related to the localhost secure issues? |
I believe this is unrelated. Seems Safari's CORS validation of public Origin follows different rules than Chromium/Firefox, but I don't own a Mac to confirm if the issue with CORS on https://webui.ipfs.io loaded in Safari is real. @rafaelramalho19 – mind taking a look? |
@lidel I can confirm that I can replicate this issue on Safari only This appears to be an old issue with Safari, and I couldn't find a direct approach to fixing this (https://stackoverflow.com/questions/39076180/https-page-was-not-allowed-to-run-insecure-content-from-safari-extension-uri) |
This is not to do with CORs, this is because we're trying to access content in an insecure way from a secure location - the page is loaded over https but the API request is made over http. You used to be able to turn this off as a Safari preference but it's been removed, which is probably for the best. I'm going to close this, it's a duplicate of ipfs/ipfs-webui#1541 |
if i am running the webpage on http://localhost:3000 it works for both Safari & Chrome & Firefox...
however if i am running the webpage on https://mydomain.com only Safari fail to connect to the go-ipfs daemon while all the other browser still work on the https://mydomain.com. I think the CORS header at the api got a different requirements or format that Safari ask for.
and actually it happen the same for https://webui.ipfs.io/ too... safari 13.1.1 would be rejected to gain access to the local go-ipfs daemon
in the mean time, Brave browser just works
in short, http://localhost:xxxx works on all browser, https://xxx.com only Safari would fail
and i think it's a very old problem for long...
https://stackoverflow.com/questions/16824661/cors-request-not-working-in-safari
Originally posted by @thienpow in #3130 (comment)
The text was updated successfully, but these errors were encountered: