Contexts (main, events, http, server, location) in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main context in an nginx configuration?

The main context is the top-level block in nginx configuration. It contains global settings that affect the entire nginx server, such as user permissions and worker processes.

beginner

What is the purpose of the events context in nginx?

The events context configures how nginx handles connections, such as setting the maximum number of simultaneous connections and the event model used.

beginner

Describe the http context in nginx.

The http context defines settings for handling HTTP traffic. It includes configurations like server blocks, MIME types, and proxy settings.

beginner

What does the server context do inside the http context?

The server context defines a virtual server. It specifies settings like the domain name, port, and SSL certificates for a specific website or service.

beginner

Explain the role of the location context in nginx.

The location context is inside a server block. It matches specific URL patterns and defines how to process requests for those URLs, such as serving files or proxying requests.

Which nginx context is used to set global worker process settings?

A events

B main

C http

D server

The main context is the top-level block where global settings like worker processes are configured.

Where do you configure the maximum number of simultaneous connections in nginx?

A server context

B http context

C location context

D events context

The events context handles connection-related settings, including max connections.

Which context contains server blocks in nginx?

A http

B main

C events

D location

The http context contains server blocks that define virtual servers.

Inside which context do you define domain names and ports for websites?

A location

B main

C server

D events

The server context defines domain names, ports, and SSL settings for a website.

What is the purpose of the location context?

A Match URL patterns and handle requests

B Configure connection limits

C Set global worker processes

D Define virtual servers

The location context matches URL patterns and defines how to handle those requests.

Explain the hierarchy and purpose of nginx contexts: main, events, http, server, and location.

Think of nginx config like a building with floors and rooms, each context is a level with specific roles.

How would you organize nginx configuration to serve multiple websites with different URL paths?

Imagine each website is a separate store, and each URL path is a different aisle inside the store.

Practice

1. Which nginx context is used to define global settings that affect the entire nginx server?

easy

A. main

B. http

C. server

D. location

Solution

1. Step 1: Understand nginx context scopes

   The main context is the top-level context for global settings.

2. Step 2: Differentiate other contexts

   The http context is for HTTP-specific settings, server for virtual hosts, and location for URL matching.

3. Final Answer:

   main -> Option A

4. Quick Check:

   Global settings = main [OK]

Hint: Global settings go in main context only [OK]

Common Mistakes:

• Confusing http with main context
• Placing global settings inside server or location
• Thinking events is for global settings

2. Which of the following is the correct way to nest the server context inside nginx configuration?

easy

A. main { server { ... } }

B. http { server { ... } }

C. events { server { ... } }

D. location { server { ... } }

Solution

1. Step 1: Recall nginx context hierarchy

   The server context must be inside the http context.

2. Step 2: Check each option's nesting

   Only http { server { ... } } is valid nesting; others are invalid.

3. Final Answer:

   http { server { ... } } -> Option B

4. Quick Check:

   server inside http = correct [OK]

Hint: Server blocks go inside http context [OK]

Common Mistakes:

• Placing server inside main or events
• Nesting server inside location
• Confusing events with http context

3. Given this nginx snippet, what is the correct context for the listen 80; directive?

http {
  server {
    listen 80;
    location / {
      root /var/www/html;
    }
  }
}

medium

A. server

B. events

C. main

D. location

Solution

1. Step 1: Identify where listen directive belongs

   The listen directive configures the port for a virtual host, which belongs in the server context.

2. Step 2: Check the snippet structure

   In the snippet, listen 80; is inside server, which is correct.

3. Final Answer:

   server -> Option A

4. Quick Check:

   listen directive = server context [OK]

Hint: listen always goes inside server context [OK]

Common Mistakes:

• Placing listen inside location
• Thinking listen belongs in main or events
• Confusing location with server context

4. You wrote this nginx config but nginx fails to start:

events {
  server {
    worker_connections 1024;
  }
}

What is the error?

medium

A. Missing http context around server

B. worker_connections must be inside server

C. events context cannot contain any directives

D. server context cannot be inside events

Solution

1. Step 1: Understand events context usage

   The events context is for event-related directives only and cannot contain server blocks.

2. Step 2: Identify invalid nesting

   Placing server inside events is invalid and causes nginx startup failure.

3. Final Answer:

   server context cannot be inside events -> Option D

4. Quick Check:

   server inside events = invalid [OK]

Hint: server blocks never go inside events context [OK]

Common Mistakes:

• Putting server inside events
• Misplacing worker_connections inside server
• Confusing events with http context

5. You want to serve static files from /var/www/html only for URLs starting with /images/. Which context should you use to configure this in nginx?

hard

A. main

B. server

C. location

D. events

Solution

1. Step 1: Identify context for URL matching

   The location context is used to match specific URL patterns like /images/.

2. Step 2: Understand static file serving setup

   Inside location, you set the root directive to serve files from the desired folder.

3. Final Answer:

   location -> Option C

4. Quick Check:

   URL-specific config = location context [OK]

Hint: Use location for URL path specific settings [OK]

Common Mistakes:

• Trying to serve files from main or events
• Placing root directive in server without location
• Confusing server and location contexts