Server block structure in Nginx - Step-by-Step Execution

Process Flow - Server block structure

Start nginx config

↓

Define server block

↓

Set listen port

↓

Set server_name

↓

Define location blocks

↓

Specify root or proxy settings

↓

Close server block

↓

nginx reads next block or ends

nginx reads the config file, finds server blocks, applies settings like port, domain, and content handling inside each block.

Execution Sample

Nginx

server {
    listen 80;
    server_name example.com;
    location / {
        root /var/www/html;
    }
}

Defines a server block listening on port 80 for example.com, serving files from /var/www/html for root URL.

Process Table

Step	Config Line Read	Action Taken	Current Server Block State	Notes
1	server {	Start new server block	server block started, empty settings	Begin server block parsing
2	listen 80;	Set listen port to 80	listen=80	Server listens on port 80
3	server_name example.com;	Set server_name	listen=80, server_name=example.com	Domain set for this server
4	location / {	Start location block for /	listen=80, server_name=example.com, location=/ started	Defines root URL handling
5	root /var/www/html;	Set root directory	location=/ root=/var/www/html	Files served from this directory
6	}	Close location block	location block closed	End location settings
7	}	Close server block	server block closed with listen=80, server_name=example.com, location root set	Server block complete
8	EOF	End of config file	All server blocks parsed	nginx ready to use this config

💡 Reached end of server block and config file; nginx has full server block settings.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
listen	unset	80	80	80	80
server_name	unset	unset	example.com	example.com	example.com
location	unset	unset	unset	/	/
root	unset	unset	unset	/var/www/html	/var/www/html

Key Moments - 3 Insights

Why do we need to close the location and server blocks with '}'?

Each '}' tells nginx the current block ends. Without it, nginx can't know where settings stop. See execution_table steps 6 and 7 where blocks close.

What happens if we omit the listen directive?

nginx uses default port 80 if listen is missing. In execution_table step 2, listen is set explicitly; if missing, nginx assumes 80.

Can we have multiple location blocks inside one server block?

Yes, each location handles different URL paths. This example shows one location at step 4-6, but more can be added similarly.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What is the server_name set to?

A unset

B localhost

C example.com

D 80

💡 Hint

Check the 'Current Server Block State' column at step 3 in execution_table.

At which step does nginx finish reading the location block?

A Step 4

B Step 6

C Step 5

D Step 7

💡 Hint

Look for the action 'Close location block' in execution_table.

If we change 'listen 80;' to 'listen 8080;', what changes in variable_tracker after step 2?

A listen changes to 8080

B server_name changes to 8080

C root changes to 8080

D No change

💡 Hint

Variable 'listen' is set at step 2; check variable_tracker for 'listen' values.

Concept Snapshot

server {
  listen [port];          # Port to listen on (default 80)
  server_name [domain];   # Domain name for this server
  location [path] {       # URL path handling
    root [directory];     # Files served from here
  }
}
Close blocks with '}' to end settings.

Full Transcript

This visual execution shows how nginx reads a server block configuration. It starts with 'server {' to open the block, then sets the listen port and server_name. Inside, it defines a location block for URL path handling, setting the root directory for files. Each block is closed with '}'. Variables like listen, server_name, location, and root update step-by-step. Key points include the need to close blocks properly and default values if some directives are missing. The quiz checks understanding of server_name setting, block closing steps, and variable changes when modifying listen port.