Why CORS matters for APIs in Express - See It in Action

Why CORS Matters for APIs

📖 Scenario: You are building a simple Express API that will be accessed by a web page hosted on a different domain. To allow this, you need to understand and configure CORS (Cross-Origin Resource Sharing) properly.

🎯 Goal: Build a basic Express API server that allows cross-origin requests from a specific domain using CORS middleware.

📋 What You'll Learn

Create an Express app with a single GET route at /data that returns JSON data.

Add a configuration variable to specify the allowed origin for CORS.

Use the cors middleware with the allowed origin configuration.

Start the Express server listening on port 3000.

💡 Why This Matters

🌍 Real World

APIs often serve data to web pages hosted on different domains. Browsers block cross-origin requests by default for security. CORS lets you specify which domains can access your API safely.

💼 Career

Understanding and configuring CORS is essential for backend developers working with APIs that serve frontend applications on different domains or ports.

1

Set up Express app with a GET route

Create an Express app by requiring express and calling express(). Then add a GET route at /data that sends JSON { message: 'Hello from API' }.

Express

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

// Your code here

Hint

Use app.get('/data', (req, res) => { ... }) to create the route.

2

Add allowed origin configuration

Create a constant called allowedOrigin and set it to the string 'http://example.com' to specify the allowed domain for CORS.

Express

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

app.get('/data', (req, res) => {
  res.json({ message: 'Hello from API' });
});

// Your code here

Hint

Define allowedOrigin as a string with the exact URL.

3

Use CORS middleware with allowed origin

Require the cors package and use it as middleware in the Express app with an options object setting origin to allowedOrigin.

Express

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

const allowedOrigin = 'http://example.com';

// Your code here

app.get('/data', (req, res) => {
  res.json({ message: 'Hello from API' });
});

Hint

Use app.use(cors({ origin: allowedOrigin })) to enable CORS for the allowed origin.

4

Start the Express server

Add app.listen to start the server on port 3000 with a callback that does nothing.

Express

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

const allowedOrigin = 'http://example.com';

app.use(cors({ origin: allowedOrigin }));

app.get('/data', (req, res) => {
  res.json({ message: 'Hello from API' });
});

// Your code here

Hint

Use app.listen(3000, () => {}) to start the server.

Practice

1. What is the main reason CORS is important for APIs in Express?

easy

A. It encrypts the data sent by the API.

B. It speeds up the API response time.

C. It automatically logs all API requests.

D. It controls which websites can access your API to protect it.

Solution

1. Step 1: Understand CORS purpose

   CORS stands for Cross-Origin Resource Sharing and it controls which websites can call your API.

2. Step 2: Identify protection role

   By controlling access, CORS protects your API from unwanted or malicious websites.

3. Final Answer:

   It controls which websites can access your API to protect it. -> Option D

4. Quick Check:

   CORS controls access = D [OK]

Hint: Remember: CORS controls access, not speed or encryption [OK]

Common Mistakes:

• Thinking CORS speeds up API
• Confusing CORS with logging
• Believing CORS encrypts data

2. Which Express middleware is commonly used to enable CORS?

easy

A. cors

B. express-session

C. body-parser

D. morgan

Solution

1. Step 1: Recall Express middleware for CORS

   The npm package named 'cors' is the standard middleware to enable CORS in Express.

2. Step 2: Identify other middleware roles

   express-session manages sessions, body-parser parses request bodies, morgan logs requests, none handle CORS.

3. Final Answer:

   cors -> Option A

4. Quick Check:

   Enable CORS with 'cors' middleware = B [OK]

Hint: Use 'cors' package to enable CORS in Express apps [OK]

Common Mistakes:

• Choosing body-parser for CORS
• Confusing logging middleware with CORS
• Using session middleware for CORS

3. What will happen if an API does NOT set CORS headers and a browser tries to call it from another website?

medium

A. The browser will block the request due to CORS policy.

B. The API will respond faster without CORS headers.

C. The API will automatically allow all websites.

D. The browser will ignore CORS and allow the request.

Solution

1. Step 1: Understand browser CORS enforcement

   Browsers enforce CORS by blocking cross-origin requests if the server does not send proper CORS headers.

2. Step 2: Identify consequences of missing CORS headers

   Without CORS headers, the browser blocks the request; the API itself may respond but browser denies access.

3. Final Answer:

   The browser will block the request due to CORS policy. -> Option A

4. Quick Check:

   Missing CORS headers = browser blocks request = A [OK]

Hint: No CORS headers means browser blocks cross-site calls [OK]

Common Mistakes:

• Thinking API blocks request instead of browser
• Assuming API allows all without CORS
• Believing browser ignores CORS

4. Consider this Express code snippet:

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

app.get('/data', (req, res) => {
  res.json({ message: 'Hello' });
});

app.listen(3000);

What is missing to allow cross-origin requests safely?

medium

A. Adding a body-parser middleware.

B. Changing app.get to app.post.

C. Adding CORS middleware to set proper headers.

D. Using HTTPS instead of HTTP.

Solution

1. Step 1: Identify missing CORS headers

   The code does not include any middleware to set CORS headers, so cross-origin requests will be blocked by browsers.

2. Step 2: Recognize correct fix

   Adding CORS middleware (like 'cors' package) will add headers to allow safe cross-origin requests.

3. Final Answer:

   Adding CORS middleware to set proper headers. -> Option C

4. Quick Check:

   Add CORS middleware to allow cross-origin = A [OK]

Hint: Add 'cors' middleware to fix cross-origin blocking [OK]

Common Mistakes:

• Thinking HTTP method change fixes CORS
• Confusing body parsing with CORS
• Believing HTTPS alone solves CORS

5. You want your Express API to allow only requests from https://example.com but block others. Which CORS configuration achieves this?

hard

A. app.use(cors());

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

C. app.use(cors({ origin: '*' }));

D. app.use(cors({ methods: ['GET', 'POST'] }));

Solution

1. Step 1: Understand origin option in CORS

   The 'origin' option in the cors middleware specifies which website origins are allowed to access the API.

2. Step 2: Match requirement to configuration

   Setting origin to 'https://example.com' allows only that site; '*' allows all, no origin restricts, methods restrict HTTP verbs only.

3. Final Answer:

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

4. Quick Check:

   Restrict origin to example.com = C [OK]

Hint: Set origin to specific URL to restrict access [OK]

Common Mistakes:

• Using '*' allows all origins, not restricted
• Omitting origin allows all by default
• Confusing methods with origin restriction