Will a fetch with the GET method be cached or memoized even when it results in errors?

[Nader-CS]

Summary

Will a fetch with the GET method be cached or memoized even when it results in errors?

Additional information

No response

Example

No response

[icyJoseph]

If I remember correctly, it is only 200 status requests that get cached by the patched fetch, source:

• next.js/packages/next/src/server/lib/patch-fetch.ts

  Line 625 in 0dcee14

  res.status === 200 &&

 GET / 200 in 1443ms
 │ GET https://pokeapi.co/api/v2/pokemon/foooooo 404 in 1379ms (cache skip)
 │ │ Cache skipped reason: (cache-control: no-cache (hard refresh))
 GET / 200 in 463ms
 │ GET https://pokeapi.co/api/v2/pokemon/foooooo 404 in 439ms (cache skip)
 │ │ Cache skipped reason: (cache-control: no-cache (hard refresh))
 GET / 200 in 125ms

vs

 GET / 200 in 144ms
 │ GET https://pokeapi.co/api/v2/pokemon/ditto 200 in 81ms (cache skip)
 │ │ Cache skipped reason: (cache-control: no-cache (hard refresh))
 GET / 200 in 29ms
 │ GET https://pokeapi.co/api/v2/pokemon/ditto 200 in 1ms (cache hit)
 GET / 200 in 29ms
 │ GET https://pokeapi.co/api/v2/pokemon/ditto 200 in 1ms (cache hit)

I might do some more testing, but I think we are on right track with 200's. cache from React is a different thing though:

• https://react.dev/reference/react/cache#caveats

cachedFn will also cache errors. If fn throws an error for certain arguments, it will be cached, and the same error is re-thrown when cachedFn is called with those same arguments.

[Nader-CS]

thank you sir.