You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a website hosted with Kubo, and I'm noticing a caching issue between IPFS and IPNS which is reproducible on at least https://ipfs.io and https://dweb.link (though I suspect this is a universal issue with Kubo/Boxo, not sure where this issue should live). Here's what I'm doing:
Navigate to cid.ipfs.gateway.tld, content loads fine and is evidently cached.
Navigate to cid.ipfs.gateway.tld/blog/, content loads fine and is evidently cached.
Navigate to key.ipns.gateway.tld (pointing to the same CID), content loads fine, even if it takes quite a while since IPNS kinda sucks speed wise.
But then, navigate to key.ipns.gateway.tld/blog/, and the content will take ages to load (or in reality, it'll timeout 95% of the time) even though cid.ipfs.gateway.tld/blog/ is still evidently cached.
If I were to guess, the gateway doesn't know key's cache can be shared with cid's cache, and so it has to do a fresh resolution to find it. It could also be that each path is actually incurring an extra IPNS resolution for no reason, but this is just a suspicious based on the amount of time it takes when the content does load.
The text was updated successfully, but these errors were encountered:
Checklist
Installation method
third-party binary
Version
Config
Description
I have a website hosted with Kubo, and I'm noticing a caching issue between IPFS and IPNS which is reproducible on at least https://ipfs.io and https://dweb.link (though I suspect this is a universal issue with Kubo/Boxo, not sure where this issue should live). Here's what I'm doing:
cid.ipfs.gateway.tld
, content loads fine and is evidently cached.cid.ipfs.gateway.tld/blog/
, content loads fine and is evidently cached.key.ipns.gateway.tld
(pointing to the same CID), content loads fine, even if it takes quite a while since IPNS kinda sucks speed wise.key.ipns.gateway.tld/blog/
, and the content will take ages to load (or in reality, it'll timeout 95% of the time) even thoughcid.ipfs.gateway.tld/blog/
is still evidently cached.If I were to guess, the gateway doesn't know
key
's cache can be shared withcid
's cache, and so it has to do a fresh resolution to find it. It could also be that each path is actually incurring an extra IPNS resolution for no reason, but this is just a suspicious based on the amount of time it takes when the content does load.The text was updated successfully, but these errors were encountered: