Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit fb43e39

Browse files
Update article.md
1 parent 806e371 commit fb43e39

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎5-network/06-fetch-api/article.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -217,8 +217,8 @@ Normally, when a document is unloaded, all associated network requests are abort
217217

218218
It has a few limitations:
219219

220-
- We can't send megabytes: the body limit for `keepalive` requests is 64kb.
220+
- We can't send megabytes: the body limit for `keepalive` requests is 64KB.
221221
- If we need to gather a lot of statistics about the visit, we should send it out regularly in packets, so that there won't be a lot left for the last `onunload` request.
222-
- This limit applies to all `keepalive` requests together. In other words, we can perform multiple `keepalive` requests in parallel, but the sum of their body lengths should not exceed 64kb.
222+
- This limit applies to all `keepalive` requests together. In other words, we can perform multiple `keepalive` requests in parallel, but the sum of their body lengths should not exceed 64KB.
223223
- We can't handle the server response if the document is unloaded. So in our example `fetch` will succeed due to `keepalive`, but subsequent functions won't work.
224224
- In most cases, such as sending out statistics, it's not a problem, as server just accepts the data and usually sends an empty response to such requests.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /