The IPFS api is nice and simple, but can cause problems for people wanting to use it as a gateway to serve images. A request for the wrong hash could cause ipfsd to start fetching a ton of data that is not actually desired.
The solutions I have at the moment are to do ipfs file ls first and then fetch, but that requires me to set up my own middleware when it would be nice to have the daemon fetch it for me.
Hrm... adding some more gateway config to set an upper limit on request sizes might be useful. Could also throw in other options at the same time like timeouts, rate limits, etc
And a completely readonly mode would be nice too.
Yeah, purely readonly would be nice.
And a completely readonly mode would be nice too.
There is now Gateway.NoFetch option in config
Here is the link to the docs for Gateway.NoFetch.