Configuring allowed origins in Express - Quick Revision & Summary

Recall & Review

beginner

What is the purpose of configuring allowed origins in an Express app?

It controls which websites can access your server resources, helping to prevent unauthorized cross-site requests.

beginner

How do you enable CORS with specific allowed origins in Express?

Use the 'cors' middleware and pass an options object with an 'origin' property listing allowed URLs.

beginner

Code snippet: What does this do?

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

It allows only requests coming from 'https://example.com' to access the Express server resources.

intermediate

How can you allow multiple origins in Express CORS configuration?

Pass a function to the 'origin' option that checks if the request origin is in a list of allowed URLs and calls the callback accordingly.

beginner

Why is it important to configure allowed origins carefully?

Because allowing all origins (using '*') can expose your server to security risks by letting any website access your resources.

What does CORS stand for in Express apps?

A Cross-Object Resource Sharing

B Cross-Origin Resource Sharing

C Client-Origin Resource Setup

D Cross-Origin Request Security

CORS means Cross-Origin Resource Sharing, a way to control resource access from different origins.

Which Express middleware is commonly used to configure allowed origins?

A cors

B helmet

C body-parser

D morgan

The 'cors' middleware is used to configure allowed origins and handle CORS in Express.

What happens if you set origin to '*' in CORS options?

A Only localhost can access

B No origins are allowed

C All origins are allowed

D Only HTTPS origins are allowed

Setting origin to '*' allows all websites to access your server resources.

How can you restrict CORS to multiple specific origins?

A Use a function to check the origin and allow or deny

B Set origin to an array of URLs

C Set origin to true

D Use multiple app.use(cors()) calls

Using a function lets you check the request origin against a list and decide to allow or deny.

Why should you avoid allowing all origins in production?

A It slows down the server

B It disables HTTPS

C It can cause syntax errors

D It exposes your server to security risks

Allowing all origins can let any website access your server, risking data leaks or attacks.

Explain how to configure allowed origins in an Express app using the 'cors' middleware.

Think about how to tell Express which websites can talk to your server.

Why is configuring allowed origins important for web app security?

Consider what could happen if any website could access your server.

Practice

1. What is the main purpose of configuring allowed origins in an Express app using cors middleware?

easy

A. To encrypt data sent between client and server

B. To speed up the server response time

C. To control which websites can access your server resources

D. To log all incoming requests

Solution

1. Step 1: Understand what allowed origins mean

   Allowed origins specify which websites are permitted to make requests to your server.

2. Step 2: Identify the role of cors middleware

   The cors middleware in Express helps set these allowed origins to control access.

3. Final Answer:

   To control which websites can access your server resources -> Option C

4. Quick Check:

   Allowed origins = control access [OK]

Hint: Allowed origins control access, not speed or encryption [OK]

Common Mistakes:

• Confusing allowed origins with encryption
• Thinking it speeds up server
• Assuming it logs requests

2. Which of the following is the correct way to allow only 'https://example.com' as an origin using the cors middleware in Express?

easy

A. app.use(cors({ origin: [https://example.com] }));

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

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

D. app.use(cors(https://example.com));

Solution

1. Step 1: Check the correct option name for allowed origins

   The correct option is origin, not origins.

2. Step 2: Verify the value type for origin

   It accepts a string for a single allowed origin, so 'https://example.com' is correct.

3. Final Answer:

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

4. Quick Check:

   Option name is origin, value is string [OK]

Hint: Use 'origin' option with string for single allowed site [OK]

Common Mistakes:

• Using 'origins' instead of 'origin'
• Passing array for single origin string
• Calling cors without options

3. Given this Express code snippet, what will be the result when a request comes from 'https://allowed.com'?

const cors = require('cors');
app.use(cors({ origin: ['https://allowed.com', 'https://other.com'] }));

medium

A. The request will be allowed because 'https://allowed.com' is in the list

B. The request will be blocked due to invalid origin format

C. The request will be allowed only if it uses POST method

D. The request will be blocked because origin must be a string

Solution

1. Step 1: Understand the origin option accepts an array

   The origin option can accept an array of allowed origins to permit multiple sites.

2. Step 2: Check if 'https://allowed.com' is in the array

   Since 'https://allowed.com' is listed, requests from it will be allowed.

3. Final Answer:

   The request will be allowed because 'https://allowed.com' is in the list -> Option A

4. Quick Check:

   Array of origins allows listed sites [OK]

Hint: Array of origins lets listed sites access [OK]

Common Mistakes:

• Thinking origin must be string only
• Assuming method affects origin check
• Believing array format causes error

4. Identify the error in this Express CORS setup that aims to allow only 'https://site.com':

app.use(cors({ origin: 'https://site.com', methods: ['GET', 'POST'] }));
app.use(cors());

medium

A. Calling cors() twice causes conflict and overrides settings

B. The methods option is invalid in cors middleware

C. The origin value should be an array, not a string

D. Missing next() call in middleware

Solution

1. Step 1: Check middleware usage order

   Calling cors() twice means the second call overrides the first, ignoring origin restrictions.

2. Step 2: Confirm methods option is valid

   The methods option is valid to restrict HTTP methods, so no error there.

3. Final Answer:

   Calling cors() twice causes conflict and overrides settings -> Option A

4. Quick Check:

   Multiple cors calls override previous config [OK]

Hint: Only call cors once with all options [OK]

Common Mistakes:

• Calling cors middleware multiple times
• Thinking origin must be array always
• Ignoring middleware order effects

5. You want to allow requests only from origins that end with '.trusted.com' dynamically in Express. Which cors configuration correctly implements this?

hard

A. app.use(cors({ origin: ['*.trusted.com'] }));

B. app.use(cors({ origin: (origin, callback) => { if (origin.includes('.trusted.com')) callback(null, true); else callback(new Error('Not allowed')); } }));

C. app.use(cors({ origin: '/^https:\/\/.*\.trusted\.com$/' }));

D. app.use(cors({ origin: (origin, callback) => { if (origin.endsWith('.trusted.com')) callback(null, true); else callback(new Error('Not allowed')); } }));

Solution

1. Step 1: Understand dynamic origin checking

   To allow origins ending with '.trusted.com', a function can check the origin string dynamically.

2. Step 2: Evaluate each option's approach

   app.use(cors({ origin: (origin, callback) => { if (origin.endsWith('.trusted.com')) callback(null, true); else callback(new Error('Not allowed')); } })); uses a function with endsWith to precisely match the domain ending, which is correct. app.use(cors({ origin: ['*.trusted.com'] })); uses wildcard string which is not supported. app.use(cors({ origin: '/^https:\/\/.*\.trusted\.com$/' })); uses regex but cors does not accept regex directly. app.use(cors({ origin: (origin, callback) => { if (origin.includes('.trusted.com')) callback(null, true); else callback(new Error('Not allowed')); } })); uses includes which may allow unwanted matches.

3. Final Answer:

   app.use(cors({ origin: (origin, callback) => { if (origin.endsWith('.trusted.com')) callback(null, true); else callback(new Error('Not allowed')); } })); -> Option D

4. Quick Check:

   Use function with endsWith for dynamic origin [OK]

Hint: Use function with endsWith() to allow domain patterns [OK]

Common Mistakes:

• Using wildcard strings in origin array
• Passing regex directly as origin
• Using includes() instead of endsWith()