conico974
conico974
> @conico974 is this getting called?https://github.com/conico974/sst/blob/cf85d5dd087f1e68436d7049fc324ca82ec84619/packages/sst/src/constructs/NextjsSite.ts#L249-L253 > > I did a brief test and `x-open-next-cache-key` wasn't listed in allowed headers. It seems only `SsrSite.buildDefaultServerCachePolicyProps()` is called. Looks like you're right,...
You do need to add the accept headers, otherwise it might send the wrong format to the end user https://github.com/vercel/next.js/blob/ffafad2c35a3f9677bb520f68e989f58f192b931/packages/next/src/server/image-optimizer.ts#L712
Tested this in V3, it works just fine there for me. If you guys can confirm in your app or provide a reproduction.
I'm going to close this old issue. If that's still an issue, reopen and provide a reproduction
Could you create a minimum repro ? rc14 is the one with broken redirect for me, and rc15 does work for all the e2e tests with redirect https://github.com/sst/open-next/blob/v3-rc/examples/app-router/next.config.js
Link to the discord threads discussing this https://discord.com/channels/983865673656705025/1230482660913184800 TLDR; This is an issue with lambda itself and depending on the region and the account, you might not experience this issue...
Fixed in [3.0.3](https://github.com/sst/open-next/releases/tag/v3.0.3) Be aware that there is another issue with streaming that cannot be fixed by us but only by aws. See https://discord.com/channels/983865673656705025/1249368592558985247
There is some basic support for Cloudflare Workers in [OpenNext V3](https://github.com/sst/open-next/releases/tag/v3.0.0). Right now the middleware and app router api route can work in Cloudflare workers. (Even if no IAC tool...
For full support : https://github.com/opennextjs/opennextjs-cloudflare