doc: clarify fetch cache behavior#63333
Closed
MukundaKatta wants to merge 1 commit into
Closed
Conversation
Contributor
|
It seems you are using a LLM to open PRs at a rate that's not humanely sustainable, without following up at all on the feedback received, please stop, this is not bringing any value and is wasting our time. If you keep opening more PRs, you'll get blocked. |
Author
|
Fair feedback, thanks for being direct. I've closed the 16 still-open ones and I'm stepping back from new PRs here while I rethink how I'm contributing. Sorry for the noise. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs: #47935
This clarifies that Node.js does not implement a browser-style HTTP cache for
fetch(), and that compatibility options such ascachedo not cause repeated requests to reuse cached responses.Testing