Skip to content

doc: clarify fetch cache behavior #63333

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MukundaKatta wants to merge 1 commit into from
+4 −0
Closed

doc: clarify fetch cache behavior #63333

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions doc/api/globals.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -567,6 +567,10 @@ The implementation is based upon [undici](https://undici.nodejs.org), an HTTP/1.
written from scratch for Node.js. You can figure out which version of `undici` is bundled
in your Node.js process reading the `process.versions.undici` property.

Node.js does not implement a browser-style HTTP cache for `fetch()`. Options
such as `cache` are accepted for Web API compatibility, but do not make repeated
requests reuse cached responses.

### Custom dispatcher

You can use a custom dispatcher to dispatch requests passing it in fetch's options object.
Expand Down
Loading