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
Gate only IPFS fetching on the gateway option, not cached content
isValidURL treated ipfs:// URIs as invalid whenever the gateway option
was off, and CacheManager consults that check before every cache path
lookup. Content that was downloaded and hash-verified while the option
was on therefore became unservable the moment it was switched off —
the cached bytes could not be served, checksummed, or evicted even
though serving a local file involves no gateway request (Bugbot,
PR Chia-Network#3029).
- isValidURL is now a structural check only: ipfs URIs are validated
via their gateway form regardless of the preference.
- Fetching is gated where it happens instead: downloadFile,
fetchBuffer, and fetchJSON resolve their request URL through a new
toFetchableUrl, which throws IpfsGatewayDisabledError for ipfs URIs
while the option is off.
- CacheManager rethrows that error instead of persisting it as a cache
ERROR entry, so flipping the option on retries cleanly - a persisted
'disabled' error would have poisoned the entry (only transient errors
are ever retried).
- The single-download IPC handler drops ipfs URLs while the option is
off instead of handing Chromium a URL it silently fails on.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017NXWAjaHb9SFafLeguTHd8
0 commit comments