Are redirects in next.config.js supported?

[kevin-mitchell]

My ultimate goal is this (so if you have a better suggestion that totally avoids the problem I'm open to that as well :)):

I want to redirect www.mydomain.tokyo to mydomain.tokyo.

An "easy" way to do this I thought would be to use Next.js functionality by adding this to next.config.js:

module.exports = {
  reactStrictMode: true,
 ...
...
  async redirects() {
    return [
      {
        source: '/:path*',
        has: [{ type: 'host', value: 'www.mydomain.tokyo' }],
        destination: 'https://mydomain.tokyo/:path*',
        permanent: true
      },
...

Unfortunately as far as I can tell, at least for me, this does not work.

Why it doesn't it work I don't know - I am wondering if it's because the origin host / hostname / domain isn't passed in to the handling function(s). I made a simple "API Route" like this:

import type { NextRequest} from "next/server";
import { NextResponse } from "next/server";

export function GET(input: NextRequest): NextResponse {

  console.log(input.nextUrl.hostname);
  console.log(input.nextUrl.nextUrl.host);
  console.log(input.headers...);

...

}

and my Next.js project HOSTED IN AWS I see localhost:3000 - everywhere - nowhere do I see mydomain.tokyo - I assume this is because indeed the server handler is executed this way, but I guess I'm not entirely certain what to expect.

I had hoped somewhere in NextRequest I could see the original domain coming in through CloudFront and then magically I could just use that in the next.config.js, but as far as I can tell it's not in the headers or anywhere else.

Am I missing anything? Is this an issue?

[kevin-mitchell]

Unfortunately I'm uncertain as to what was wrong, but I do know that for some reason updating the version of open-next I was building with and using the latest beta.3 version of this project resolved the issue. Redirects seem to be working as expected now.

[khuezy]

a newer version of open-next fixed the host from localhost:3000 => yourdomain.com

[kevin-mitchell]

Thanks for letting me know, it was really bugging me. Sometimes I feel so stupid, I spent more than an hour trying to figure out how CloudFront host was supposed to be passed to the Lambda function and to next, but never figured it out. I didn't give up, but I did do the "well, maybe I'll just update things and hope it magically starts working" - which it did. So I failed to solve the issue myself.

I might go see if I can find the commit that fixed it with open-next. Thanks again!

[khuezy]

https://github.com/sst/open-next/pull/169/files#diff-b70e8a66ef8563ad10a922309942524fd5ab3dcc85dec0690c5d90e200dd09f5R22