Accessing non-existing hash key using REST #120
Comments
|
The daemon doesn't know that the requested object does not exist. It has no way to know it, and just keeps looking for it in the network. |
|
Does this mean that web service will not return any response (like status or time out)? |
|
It will eventually time out. The public gateway at ipfs.io times out after 30 minutes, I'm not sure what the timeout of the daemon's gateway itself is -- definitely more than 30 minutes though. Do you want to be able to tell if an object does not exist? You could specify a request timeout with the HTTP/REST library or tool you are using. |
|
You can also add a timeout yourself with the On Wed, May 11, 2016 at 12:01 PM Lars Gierth notifications@github.com
|
|
Thank you lgierth. I set the read timeout on the connection and get immediate response |
|
This issue has been moved https://discuss.ipfs.io/t/accessing-non-existing-hash-key-using-rest/472. |
biljanaLukovic commentedMay 11, 2016
I have install and configured ipfs version 0.4.0. Happy path works eg. I can put an item into ipfs and retrieve it by produced hash. However, the service does not return when 'cat' looks for non existing hash code.
Example with valid hash code:
http://127.0.0.1:5001/api/v0/cat/QmckRHhKxcrp4Y2miz9hpAzFk2fepenrQCT524VYrL9LKY
Any changes in the supplied hash code will cause server to hung.
Attached is my config file.
Thanks
B
config.txt
The text was updated successfully, but these errors were encountered: