-
Notifications
You must be signed in to change notification settings - Fork 198
Custom App Hosting Headers for NextJS #304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…om-apphosting-headers
| key: "x-fah-adapter", | ||
| value: `nextjs-${adapterMetadata.adapterVersion}`, | ||
| }, | ||
| ...(middlewareExists(middlewareManifest) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we be adding a separate x-fah-middleware header entry for each of the middleware matchers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's what we eventually want to do. I believe we agreed for now that we'll add this header if there is a middleware at all.
Update NextJS Adapter to:
x-fah-adapterheader that indicates adapter name + versionroute-manifest.jsonfile in the standalone folder to addx-fah-adapterheader.x-fah-middlewareheader for apps that have a middleware.middleware-manifest.jsonfile to check if there are any middlewares used by the app, and updates theroute-manifest.jsonfile to addx-fah-middlewareheader.Manual Testing:
Depends on #305