60488e68e3
* Fix broken links for Data Fetching * Fix link data fetching doc * Improve link file paths * Update errors/large-page-data.md Co-authored-by: Steven <steven@ceriously.com> * Update links * Fix linting * Lint tests * Lint tests Co-authored-by: Steven <steven@ceriously.com> Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
19 lines
1.1 KiB
Markdown
19 lines
1.1 KiB
Markdown
# Must not access ServerResponse after getServerSideProps() resolves
|
||
|
||
#### Why This Error Occurred
|
||
|
||
`getServerSideProps()` surfaces a `ServerResponse` object through the `res` property of its `context` arg. This object is not intended to be accessed or changed after `getServerSideProps()` resolves.
|
||
|
||
This is because the framework tries to optimize when items like headers or status codes are flushed to the browser. If they are changed after `getServerSideProps()` completes, we can't guarantee that the changes will work.
|
||
|
||
For this reason, accessing the object after this time is disallowed.
|
||
|
||
#### Possible Ways to Fix It
|
||
|
||
You can fix this error by moving any access of the `res` object into `getServerSideProps()` itself or any functions that run before `getServerSideProps()` returns.
|
||
|
||
If you’re using a custom server and running into this problem due to session middleware like `next-session` or `express-session`, try installing the middleware in the server instead of `getServerSideProps()`.
|
||
|
||
### Useful Links
|
||
|
||
- [Data Fetching Docs](https://nextjs.org/docs/basic-features/data-fetching/index)
|