New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Returns 403 only for web UI #88
Comments
|
Hmmmm this is tricky. can others familiar with the web concerns here CR this? i don't have the bandwidth atm. (maybe @diasdavid @cryptix @mappum ) |
|
If I'm understanding it right, it is a CORS issue, |
|
Hmmm... I tried both 127.0.0.1 and localhost to load the web ui from and neither work at the moment. Sometimes I can coax it to work for a few minutes by aggressively restarting everything. Note: I was able to successfully use the web ui after running I hope it will stay fixed. |
|
this may be related to ipfs/kubo#1883 |
me too. ok what is going on!? |
|
It might be a header issue |
worked for me which implies the default is not being set by the code as it should be: https://github.com/ipfs/go-ipfs/blob/27eece3e81f4e946db4294702c9ac39bd86ccce6/core/corehttp/commands.go#L70 |
|
Has anyone found a fix for this yet? (beyond this workaround). Need to trace how the logic goes around here: https://github.com/ipfs/go-ipfs/blob/27eece3e81f4e946db4294702c9ac39bd86ccce6/core/corehttp/commands.go#L69 |
|
after an upgrade to consul v0.6, the web UI no longer works for me either. |
|
This should be fixed in 0.3.11 :) Please reopen if there are still problems |
|
Using FF, currently have some problem. If I edit request by removing Referer header, all works fine! |
|
Thank you @hleb-albau |
stephen304 commentedOct 16, 2015
I noticed that the web ui would stop working after a while, and permanently. The API still responds fine, but not when the UI makes the request. Chrome/firefox web tools lets you export a request to a cURL command, and I was able to export a working request (where I pasted in the api url into the address bar), and a broken request coming from the API. These results are replicated using cURL as well.
Chrome
Command from the address bar, working:
Response:
Command from the web UI, broken:
Response:
The diff of these 2 requests are as follows (working on the left, web ui on the right):

I found that removing the referrer and adding the
Cache-Control: max-age=0fixed the request:Result:
Firefox
The requests coming from firefox are a bit different.
Working, from a request coming from the URL bar:
Broken, coming from the web ui:
Diff:

P.S. Here's what the web ui looks when the api requests fail. You can see the network inspector open with the xhr filter, showing all the failed requests:

The text was updated successfully, but these errors were encountered: