Contexts (main, events, http, server, location) in Nginx - Step-by-Step Execution

Process Flow - Contexts (main, events, http, server, location)

Start: nginx.conf file

↓

main context

↓

events context

↓

http context

↓

server context

↓

location context

↓

Request handling

↓

Response sent

nginx configuration is structured in nested contexts: main, events, http, server, and location. Each context controls different parts of nginx behavior.

Execution Sample

Nginx

worker_processes  1;
events {
  worker_connections  1024;
}
http {
  server {
    location / {
      root /var/www/html;
    }
  }
}

This config sets one worker process, limits connections, and serves files from /var/www/html for requests to root location.

Process Table

Step	Context Entered	Directive Processed	Effect	Next Context
1	main	worker_processes 1;	Sets number of worker processes to 1	events
2	events	worker_connections 1024;	Limits max connections per worker to 1024	http
3	http	server { ... }	Defines HTTP server block	server
4	server	location / { ... }	Defines location block for root path	location
5	location	root /var/www/html;	Sets document root for requests	Request handling
6	Request handling	Request to /index.html	Serves file /var/www/html/index.html	Response sent
7	-	-	-	End of processing

💡 All contexts processed and request served, nginx completes handling

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
worker_processes	default (auto)	1	1	1	1	1	1
worker_connections	default (1024)	1024	1024	1024	1024	1024	1024
server_blocks	none	none	none	1 server block	1 server block	1 server block	1 server block
location_blocks	none	none	none	none	1 location block	1 location block	1 location block
document_root	none	none	none	none	none	/var/www/html	/var/www/html

Key Moments - 3 Insights

Why can't we put 'worker_connections' inside the 'http' context?

'worker_connections' must be inside the 'events' context as shown in step 2 of the execution_table. Placing it elsewhere causes nginx to reject the config.

What happens if we put 'root' directive outside the 'location' context?

'root' is valid inside 'http', 'server', or 'location' contexts, but placing it inside 'location' (step 5) scopes it specifically to that path. Outside location, it applies more broadly.

How does nginx decide which 'location' block to use?

Nginx matches the request URI against 'location' blocks defined in the 'server' context (step 4). The best match is chosen to serve the request.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What does entering the 'http' context allow you to configure?

A Define server blocks to handle HTTP requests

B Set worker process numbers

C Limit worker connections

D Serve static files directly

💡 Hint

Check the 'Directive Processed' and 'Effect' columns at step 3 in execution_table

At which step does nginx set the document root for serving files?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the 'Directive Processed' column for 'root /var/www/html;' in execution_table

If you increase 'worker_connections' to 2048, which variable_tracker value changes?

A worker_processes

B worker_connections

C server_blocks

D document_root

💡 Hint

Check the 'worker_connections' row in variable_tracker for changes

Concept Snapshot

nginx config uses nested contexts:
- main: global settings like worker_processes
- events: connection limits
- http: HTTP server configs
- server: virtual hosts
- location: URL path handling
Directives must be in correct context to work.

Full Transcript

Nginx configuration is organized in nested contexts. The main context sets global options like worker_processes. The events context controls connection limits such as worker_connections. The http context groups HTTP server settings. Inside http, server contexts define virtual hosts. Each server can have multiple location contexts to handle specific URL paths. Directives must be placed in the correct context to take effect. For example, worker_connections belongs in events, while root belongs in location or server. When nginx starts, it reads the config top-down entering each context and applying directives. When a request arrives, nginx matches it to a server and location context to serve content accordingly.