CORS configuration in Node.js - Step-by-Step Execution

Concept Flow - CORS configuration

Client sends request

↓

Server receives request

↓

Check Origin header

↓

Is Origin allowed?

No→Reject request or no CORS headers

Yes↓

Add CORS headers to response

↓

Send response back to client

This flow shows how a server checks the client's origin and adds CORS headers if allowed, enabling cross-origin requests.

Execution Sample

Node.js

const express = require('express');
const cors = require('cors');
const app = express();

app.use(cors({ origin: 'https://example.com' }));

app.get('/', (req, res) => res.send('Hello CORS!'));

app.listen(3000, () => console.log('Server running on port 3000'));

This code sets up a Node.js Express server that allows cross-origin requests only from https://example.com.

Execution Table

Step	Client Origin	Server Action	CORS Header Added	Response Sent
1	https://example.com	Check origin matches allowed origin	Access-Control-Allow-Origin: https://example.com	Hello CORS! with CORS headers
2	https://notallowed.com	Check origin does not match	No CORS headers added	Hello CORS! without CORS headers
3	No Origin header (same origin)	Origin undefined, does not match allowed origin	No CORS headers added	Hello CORS! without CORS headers

💡 Requests from allowed origins get CORS headers; others do not, controlling cross-origin access.

Variable Tracker

Variable	Start	After Request 1	After Request 2	After Request 3
req.headers.origin	undefined	https://example.com	https://notallowed.com	undefined
corsOptions.origin	https://example.com	https://example.com	https://example.com	https://example.com
CORS header added	false	true	false	false

Key Moments - 2 Insights

Why does the server add CORS headers only for some origins?

The server compares the request's Origin header to the allowed origins (see execution_table step 1 and 2). If it matches, it adds CORS headers; otherwise, it does not.

What happens if the request has no Origin header?

If no Origin header is present (usually same-origin requests), the server does not add CORS headers since it does not match the allowed origin (see execution_table step 3). Same-origin requests do not require CORS headers.

Visual Quiz - 3 Questions

Look at the execution_table, what CORS header is added when the client origin is https://example.com?

A Access-Control-Allow-Origin: *

B No CORS headers added

C Access-Control-Allow-Origin: https://example.com

D Access-Control-Allow-Methods: GET

💡 Hint

Check execution_table row 1 under 'CORS Header Added'

At which step does the server NOT add CORS headers?

A Step 1

B Step 2

C Step 3

D All steps add headers

💡 Hint

Look at execution_table rows 2 and 3 under 'CORS Header Added'

If the allowed origin changes to '*' (all origins), how would the CORS header change in step 1?

A Access-Control-Allow-Origin: *

B No CORS headers added

C Access-Control-Allow-Origin: https://example.com

D Access-Control-Allow-Methods: POST

💡 Hint

Think about how wildcard '*' allows all origins, changing the header value

Concept Snapshot

CORS configuration in Node.js:
- Server checks request Origin header
- If origin allowed, adds Access-Control-Allow-Origin header
- Use cors middleware in Express: app.use(cors({ origin: 'https://example.com' }))
- Controls which sites can access server resources
- No header means browser blocks cross-origin requests

Full Transcript

CORS configuration controls which websites can access your server's resources. When a client sends a request, the server checks the Origin header. If the origin matches allowed sites, the server adds CORS headers to the response. This tells the browser it's safe to share data. If the origin is not allowed, the server does not add these headers, so the browser blocks the response. In Node.js with Express, the cors middleware simplifies this by letting you specify allowed origins. This example allows only https://example.com. Requests from other origins get no CORS headers and are blocked by browsers. Requests without an Origin header, like same-origin requests, get no CORS headers but are allowed by browsers since they are same-origin.

Practice

1. What is the main purpose of configuring CORS in a Node.js server?

easy

A. To speed up server response time

B. To control which websites can access server resources

C. To encrypt data sent between client and server

D. To manage database connections

Solution

1. Step 1: Understand CORS role

   CORS (Cross-Origin Resource Sharing) controls which external websites can request resources from your server.

2. Step 2: Identify main purpose

   It is not about speed, encryption, or database management but about access control from different origins.

3. Final Answer:

   To control which websites can access server resources -> Option B

4. Quick Check:

   CORS controls access = A [OK]

Hint: Remember CORS = Cross-Origin Resource Sharing control [OK]

Common Mistakes:

• Confusing CORS with encryption or speed optimization
• Thinking CORS manages databases
• Assuming CORS is a security firewall

2. Which of the following is the correct way to import and use the cors middleware in an Express app?

easy

A. import cors from 'cors'; app.use(cors());

B. import cors from 'cors'; app.use(cors);

C. const cors = require('cors'); app.use(cors);

D. const cors = require('cors'); app.use(cors());

Solution

1. Step 1: Identify modern import syntax

   Using ES modules, the correct import is import cors from 'cors';.

2. Step 2: Use middleware correctly

   Middleware must be called as a function: app.use(cors()); not just cors.

3. Final Answer:

   import cors from 'cors'; app.use(cors()); -> Option A

4. Quick Check:

   Import + call middleware = D [OK]

Hint: Use import + call cors() as function [OK]

Common Mistakes:

• Forgetting parentheses when using middleware
• Mixing require and import syntax
• Using app.use(cors) without parentheses

3. Given this code snippet, what will be the CORS behavior?

import express from 'express';
import cors from 'cors';
const app = express();
app.use(cors({ origin: 'https://example.com' }));
app.get('/', (req, res) => res.send('Hello'));
app.listen(3000);

medium

A. Only requests from https://example.com will be allowed

B. Requests from any origin will be allowed

C. No requests will be allowed due to missing headers

D. Requests from localhost will be allowed only

Solution

1. Step 1: Analyze the origin option

   The cors middleware is configured with origin: 'https://example.com', which restricts access to that origin only.

2. Step 2: Understand effect on requests

   Requests from other origins will be blocked by CORS policy, so only https://example.com is allowed.

3. Final Answer:

   Only requests from https://example.com will be allowed -> Option A

4. Quick Check:

   origin restricts access = C [OK]

Hint: Check origin value to know allowed sites [OK]

Common Mistakes:

• Assuming all origins allowed by default
• Confusing origin with methods or headers
• Thinking localhost is allowed without explicit mention

4. Regarding this CORS setup code, which statement is accurate?

import express from 'express';
import cors from 'cors';
const app = express();
app.use(cors({ origin: ['https://site1.com', 'https://site2.com'] }));
app.listen(3000);

medium

A. Missing call to cors() function

B. The app.listen() call is missing a callback

C. The origin option can be an array

D. The cors package is not imported correctly

Solution

1. Step 1: Check origin option type

   The origin option in cors accepts an array directly for multiple static origins; it also supports string, boolean, regex, or function.

2. Step 2: Confirm other parts are correct

   The cors() function is called correctly, app.listen() works without callback, and import syntax is valid.

3. Final Answer:

   The origin option can be an array -> Option C

4. Quick Check:

   origin array valid = B [OK]

Hint: origin can be string, array, regex, or function [OK]

Common Mistakes:

• Thinking origin cannot accept an array
• Forgetting to call cors() as a function
• Thinking app.listen needs a callback always

5. You want to allow CORS requests only from https://trusted.com and http://localhost:3000. Which is the best way to configure the cors middleware in your Node.js app?

hard

A. Use origin as a function to check allowed origins dynamically

B. Set origin to '*' to allow all origins

C. Disable CORS middleware and handle manually

D. Set origin to an array of allowed origins directly

Solution

1. Step 1: Understand multiple origins handling

   The cors package accepts an array directly for origin with a static list of allowed origins. This is the simplest and best approach here.

2. Step 2: Evaluate options

   Use function for dynamic logic (e.g., regex or env-based). '*' allows all (insecure). Manual handling is error-prone and not recommended.

3. Final Answer:

   Set origin to an array of allowed origins directly -> Option D

4. Quick Check:

   Static multiple origins use array = C [OK]

Hint: Use array for static multiple origins [OK]

Common Mistakes:

• Using '*' to allow all origins insecurely
• Using a single string for multiple origins
• Disabling middleware instead of configuring properly