-
Notifications
You must be signed in to change notification settings - Fork 21
Issue #181 - Redefine network request in terms of Fetch #182
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.
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
base: gh-pages
Are you sure you want to change the base?
Conversation
12e289a
to
b238793
Compare
PTAL @clelland |
I want to call out #182 (comment) - I thought I left a comment, but I can't find it in the GitHub UI: I think you're suggesting that HTTP-network fetch handles both of 1) not doing a "network request" from the cache, and 2) not referencing redirects explicitly, because HTTP-network fetch handles that, and prevents serving a redirect response from cache (thus, resulting in a "network request"). Is that correct? Or did I miss the point? |
Guess it's not exported yet. 🤷 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good - one comment about some deleted text that could be useful as a note
</p> | ||
|
||
<p> | ||
A <a>request</a> MUST NOT result in a <a>network request</a> if the user |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two paragraps likely follow from fetch, but may be useful as a note
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, will swap to a Note.
This is Part 1 of N commits to address #166.
It largely just links to existing Fetch concepts.
Preview | Diff