Comments (7)
Interesting... so the problem is not as phrased by the title, thought the problem exists.
One way to see the issue is with the devtools network, and preserve logs, but another is to modify the api endpoint to:
import { NextRequest, NextResponse } from 'next/server';
export const GET = (req: NextRequest) => {
console.log('redirect called', req.nextUrl.searchParams.get('_rsc'));
return NextResponse.json({ hello: 'there' });
};
And now you see, where this is going. When you have the loading
file, Next.js serves that suspense boundary to the client, so Loading
is seen by the client.
Then the framework is making a request for _rsc data to the endpoint, not that this endpoint serves 200 + json, an at the same time the framework is making a request to the endpoint, without the _rsc query.
I'd seem that this PR, #63786, referenced in #57257 should indeed take care of this 🤔
from next.js.
We're experiencing the very same issue, which seems to have been introduced in 14.2.2
or 14.2.3
.
We temporarily downgraded to 14.2.1
, which doesn't show this weird behavior. For our use case it is critical, as the redirect involves a third party data generation API which doesn't allow the same url (incl. query params) to be called twice.
from next.js.
ah nice, what would be a more appropriate title?
from next.js.
I think the issue is still, a Double redirect when using a loading boundary and Route Handlers
From the test I see that, the intention had been to redirect to another page, not a Route Handler.
Though I am not sure I have the time to investigate a whole lot, but the issue is interesting to say the least.
from next.js.
Thanks hopefully a more appropriate title will help attract some more interest, it is slightly different as this issue is present if you redirect to another Page and a route handler. My example was a route handler as that is a cut down version of our use case (We need to do some cookie clean up and that was the only way we could think in the flow we have).
There is a work around that if the redirect is down in a child client component then you do not get the double render. However this is a bit messy and is not ideal
from next.js.
Alright, I see, the odd thing is that the test introduced by #63786 should really be guarding against that... I'll try to run the tests on this machine, to see what's up
from next.js.
Ok, I got them tests running here, and isolated to the test introduced in #63786 plus a router handler test redirect I wrote, and I can see that, the test is making sure the UI doesn't change, because the redirected to page (or my route handler), render with Date.now, so the assumption is made, should you show two different dates to the client, then you definitely did a double redirect, but that's not the entire picture.
I can see that the server makes a request with _rsc
, and one without it, where it'd seem that the UI ignores one, and uses the other, and that makes the test assumption pass.
I'll see if I can change the check to make the test fail.
from next.js.
Related Issues (20)
- Standalone Output doesn't work HOT 3
- Top Suspence fallback not work in chrome or android
- Cached function in layout and page runs twice
- Default hostname for "next start" differs from documentation HOT 1
- Docs: Migration from vite shows app router docs HOT 1
- How to use generated "Route" type (from "typedRoutes") with dynamic routes HOT 2
- Enabling Draft Mode Not Working in Next.js 14.2.5 HOT 2
- Re-exported modules from index.ts are not tree shaken
- v14 npm run lint (eslint+typescript) Not implemented correctly HOT 3
- `app/icon.tsx` and `npm run dev` with `output: "export"` HOT 2
- Next.js App Directory: Link Component Crashes on First Load with Storyblok Integration
- Docs: learn -> improving-accessibility, missing something about accessiblity HOT 3
- postcss.config.js not work with type module
- Use intercepting and parallel route with root level not working HOT 1
- Next.js downloads from fonts.googleapis.com during build HOT 1
- Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node HOT 1
- Can't use Intercepting and Parallel routes in root level HOT 3
- Error: You cannot use both an required and optional catch-all route HOT 1
- Error: You cannot use both an required and optional catch-all route
- Incorrect caching
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from next.js.