You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/docs/20-core-concepts/20-load.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -234,7 +234,7 @@ To get data from an external API or a `+server.js` handler, you can use the prov
234
234
- It can be used to make credentialed requests on the server, as it inherits the `cookie` and `authorization` headers for the page request.
235
235
- It can make relative requests on the server (ordinarily, `fetch` requires a URL with an origin when used in a server context).
236
236
- Internal requests (e.g. for `+server.js` routes) go directly to the handler function when running on the server, without the overhead of an HTTP call.
237
-
- During server-side rendering, the response will be captured and inlined into the rendered HTML by hooking into the `text`and `json` methods of the `Response` object. Note that headers will _not_ be serialized, unless explicitly included via [`filterSerializedResponseHeaders`](hooks#server-hooks-handle).
237
+
- During server-side rendering, the response will be captured and inlined into the rendered HTML by hooking into the `text`, `json`and `arrayBuffer` methods of the `Response` object. Note that headers will _not_ be serialized, unless explicitly included via [`filterSerializedResponseHeaders`](hooks#server-hooks-handle).
238
238
- During hydration, the response will be read from the HTML, guaranteeing consistency and preventing an additional network request - if you received a warning in your browser console when using the browser `fetch` instead of the `load``fetch`, this is why.
0 commit comments