CORS Error different domains | NestJS | Page 1

burnt lake Oct 25, 2022, 12:03 AM

#

Hello. When I upload NestJS server in production. I get CORS error.

Can I enable cors even when I am having two different domains (for client and server)

const app = await NestFactory.create<NestExpressApplication>(AppModule, {
  cors: true,
});

app.enableCors({
  origin: 'https://mysite.vercel.app',
  credentials: true,
});

Access to fetch at 'https://api.mysite.net/' from origin 'https://mysite.vercel.app' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.

obtuse owl Oct 25, 2022, 12:16 AM

#

Remove the cors: true option. Stick with just enableCors()

burnt lake Oct 25, 2022, 12:27 AM

#

obtuse owl Remove the `cors: true` option. Stick with just `enableCors()`

Okay, thanks. 🙂

burnt lake Oct 25, 2022, 12:51 AM

#

obtuse owl Remove the `cors: true` option. Stick with just `enableCors()`

Did I miss something to setup, in order to make authorization working on cross domains?

obtuse owl Oct 25, 2022, 12:51 AM

#

cors: true does origin: * which is invalid when sending credentials

burnt lake Oct 25, 2022, 12:52 AM

#

obtuse owl `cors: true` does `origin: *` which is invalid when sending credentials

Are we talking about the first line of my code?

obtuse owl Oct 25, 2022, 12:52 AM

#

In the NestFactory.create yes

burnt lake Oct 25, 2022, 12:52 AM

#

burnt lake Did I miss something to setup, in order to make authorization working on cross ...

User is authorized the on server, but in the fetch request it acts like unauthorized.

burnt lake Oct 25, 2022, 12:53 AM

#

obtuse owl In the `NestFactory.create` yes

I removed it according to your advice and kept the .enableCors

burnt lake Oct 25, 2022, 12:54 AM

#

burnt lake User is authorized the on server, but in the fetch request it acts like unauthor...

Is this client side related problem or server side?

obtuse owl Oct 25, 2022, 12:54 AM

#

burnt lake User is authorized the on server, but in the fetch request it acts like unauthor...

What does your client request look like?

burnt lake Oct 25, 2022, 12:54 AM

#

const requestAPI = async (
  endpoint: string,
  method: string = "GET",
  { headers, ...options }: { headers?: HeadersInit } & RequestInit = {}
) => {
  return fetch(`${process.env.SERVER_URL}${endpoint}`, {
    method,
    headers: {
      Accept: "application/json",
      "Content-Type": "application/json",
      ...headers,
    },
    credentials: "include",
    ...options,
  }).then(async (res) => {
    const data = await res.json();

    if (!res.ok) {
      throw new Error(`${data.statusCode} - ${data.message}`);
    }

    return data;
  });
};```