browser loading the old ipfs cid even after publishing new revision to w3name

Question

browser loading the old ipfs cid even after publishing new revision to w3name

pawanpaudel93 opened this issue 2 years ago · comments

This URL shows the name is referencing the new IPFS CID but still tries to load the previous CID contents in the browser. The first revision works perfectly fine but the new revisions to w3name don't load up the latest IPFS CID.

ipns://k51qzi5uqu5dm09eb5pk1af1622tn7atinj0ynaic685p9pzbinffxlmc9t82j
ipfs://bafybeic3zxymvc7jfnw6pc7scsgxvmkttvmlmho2vidl22tjxmefevy2ru

Pawan Paudel · Answer 1 · Sat Sep 17 2022 14:02:57 GMT+0800 (China Standard Time)

Now I am able to access the latest IPFS published to w3name but it takes a lot of time to switch from old to new IPFS CID completely. Is there any reason that it's taking too long to take effect ???

MJJHUA · Answer 2 · Wed Sep 21 2022 11:00:32 GMT+0800 (China Standard Time)

Same problem.
How to fix it ?

Portgas D. Kyn · Answer 3 · Fri Dec 02 2022 07:21:29 GMT+0800 (China Standard Time)

@pawanpaudel93 How did you managed to solve that ?

StephanGerbeth · Answer 4 · Fri Jan 13 2023 21:21:13 GMT+0800 (China Standard Time)

I had the same problems, when i tried to open the resulting ipns-Url directly in the browser.
If i use the w3name api, I always got the correct response with the updated revision.