Directives and blocks in Nginx - Step-by-Step Execution

Process Flow - Directives and blocks

Start parsing config

↓

Read directive or block

↓

If directive

Execute directive→Continue

↓

If block start

Enter block context→Parse inner directives

↓

Block end found?

No→Parse inner directives

Yes↓

Exit block context

→Continue

↓

End of config file

Nginx reads each line as a directive or block start. Directives execute immediately. Blocks open a new context to parse nested directives until the block ends.

Execution Sample

Nginx

http {
  server {
    listen 80;
  }
}

This config defines an http block containing a server block with a listen directive.

Process Table

Step	Config Line Read	Action	Context Stack	Resulting State
1	http {	Start http block	['http']	Entered http context
2	server {	Start server block inside http	['http', 'server']	Entered server context
3	listen 80;	Execute listen directive	['http', 'server']	Server listens on port 80
4	}	End server block	['http']	Exited server context
5	}	End http block	[]	Exited http context, config parsing done

💡 Reached end of config file, all blocks closed properly

Status Tracker

Context Stack	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5
Context Stack	[]	['http']	['http', 'server']	['http', 'server']	['http']	[]

Key Moments - 3 Insights

Why does the context stack grow when we see a block start like 'http {'?

Because blocks open a new context to group directives inside. The stack tracks nested blocks as shown in execution_table steps 1 and 2.

What happens when we reach a closing brace '}'?

The parser exits the current block context, popping it from the stack. See execution_table steps 4 and 5 where contexts are removed.

Are directives inside blocks executed immediately or delayed?

Directives are executed immediately within their current context. For example, 'listen 80;' runs at step 3 inside the 'server' block.

Visual Quiz - 3 Questions

Look at the execution table. What is the context stack after reading 'server {'?

A ['server']

B ['http']

C ['http', 'server']

D []

💡 Hint

Check the 'Context Stack' column at step 2 in the execution_table.

At which step does the parser exit the 'server' block?

A Step 4

B Step 3

C Step 5

D Step 2

💡 Hint

Look for the closing brace '}' that ends the server block in execution_table.

If the 'listen 80;' directive was missing, how would the execution_table change at step 3?

A Step 3 would still execute 'listen 80;'

B Step 3 would close the server block

C Step 3 would show no action and no change in state

D Step 3 would start a new block

💡 Hint

Without 'listen 80;', the third line read would be the closing brace '}' for the server block.

Concept Snapshot

Nginx config uses directives and blocks.
Directives end with a semicolon and run immediately.
Blocks start with '{' and group nested directives.
Blocks create a context stack that grows and shrinks.
Closing '}' ends the current block context.
Parser reads line by line, managing contexts accordingly.

Full Transcript

Nginx configuration files consist of directives and blocks. The parser reads each line. When it sees a directive, it executes it immediately. When it sees a block start like 'http {', it enters a new context and pushes it onto a stack. Inside blocks, nested directives or blocks can appear. When a closing brace '}' is found, the parser exits the current block context by popping it from the stack. This process continues until the end of the file. For example, in the sample config, the parser enters the 'http' block, then the 'server' block, executes the 'listen 80;' directive, then exits the 'server' block, and finally exits the 'http' block. This stack-based approach helps organize configuration logically and hierarchically.