archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/packages
History
Talha Zekeriya Durmuş 16131e2d49
Fix #46621 - include status code in cache (#47096) 
Fixes #46621

As explained here https://github.com/vercel/next.js/issues/46621,

> Using fetch to retrieve data inside a page on server side, the
response status code is incorrect when simply loading/reloading the
page. It looks like nextjs is caching the response without taking into
account the status code.

In following code we do not add status code information to the cache. 

https://github.com/vercel/next.js/blob/canary/packages/next/src/server/lib/patch-fetch.ts#L189-L206

However we are accessing this status code in 

https://github.com/vercel/next.js/blob/canary/packages/next/src/server/lib/patch-fetch.ts#L247-L250

---------

Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-03-13 21:37:22 -07:00
..
create-next-app Fix: Update README templates in create-next-app (#47037) 2023-03-13 13:20:39 -07:00
eslint-config-next v13.2.5-canary.2 2023-03-13 11:46:11 -07:00
eslint-plugin-next v13.2.5-canary.2 2023-03-13 11:46:11 -07:00
font Remove experimental fontLoaders option from next.config.js (#46886) 2023-03-13 21:34:43 +00:00
next Fix #46621 - include status code in cache (#47096) 2023-03-13 21:37:22 -07:00
next-bundle-analyzer v13.2.5-canary.2 2023-03-13 11:46:11 -07:00
next-codemod v13.2.5-canary.2 2023-03-13 11:46:11 -07:00
next-env v13.2.5-canary.2 2023-03-13 11:46:11 -07:00
next-mdx fix(mdx): export NextMDXOptions interface (#46441) 2023-03-13 21:13:14 -07:00
next-plugin-storybook v13.2.5-canary.2 2023-03-13 11:46:11 -07:00
next-polyfill-module v13.2.5-canary.2 2023-03-13 11:46:11 -07:00
next-polyfill-nomodule v13.2.5-canary.2 2023-03-13 11:46:11 -07:00
next-swc Detect common invalid cases for the server directive (#47069) 2023-03-13 19:20:10 +00:00
react-dev-overlay v13.2.5-canary.2 2023-03-13 11:46:11 -07:00
react-refresh-utils v13.2.5-canary.2 2023-03-13 11:46:11 -07:00