Default server handling in Nginx - Step-by-Step Execution

Process Flow - Default server handling

Client sends HTTP request

↓

Nginx receives request

↓

Check server_name in all server blocks

↓

Response sent

Nginx receives a request, tries to match the server_name in server blocks, and if none match, uses the default server block to respond.

Execution Sample

Nginx

server {
    listen 80 default_server;
    server_name _;
    return 444;
}

server {
    listen 80;
    server_name example.com;
    return 200;
}

Two server blocks: one default server that closes connections, one for example.com that returns 200 OK.

Process Table

Step	Client Request Host	Server Block Matched	Action Taken	Response
1	example.com	server_name example.com	Process example.com server block	200 OK
2	unknown.com	No match	Use default_server block	Connection closed (444)

💡 Requests with no matching server_name use the default_server block to handle the request.

Status Tracker

Variable	Start	Request 1	Request 2	Final
server_name_matched	null	example.com	null	null
used_server_block	null	example.com block	default_server block	default_server block
response_code	null	200	444	444

Key Moments - 2 Insights

Why does nginx use the default server block when the requested host does not match any server_name?

Because nginx needs a fallback to handle requests without a matching server_name, it uses the server block marked with 'default_server' as shown in execution_table row 2.

What happens if multiple server blocks listen on the same port but none is marked as default_server?

Nginx will use the first server block defined for that port as the default, similar to the default_server block behavior, ensuring requests are handled.

Visual Quiz - 3 Questions

Look at the execution table, what response does nginx send when the client requests 'example.com'?

A 200 OK

B 444 Connection Closed

C 404 Not Found

D 500 Internal Server Error

💡 Hint

Check execution_table row 1 under 'Response' column.

At which step does nginx use the default server block?

A Step 1

B Never

C Step 2

D Both steps

💡 Hint

Look at execution_table 'Server Block Matched' column for 'No match' entry.

If the default_server directive is removed, what will nginx do with unmatched requests?

A Return 404 Not Found

B Use the first server block listening on the port

C Close connection with 444

D Ignore the request

💡 Hint

Refer to key_moments second question about default_server behavior.

Concept Snapshot

Nginx default server handling:
- Nginx matches client Host header to server_name.
- If no match, uses server block with 'default_server' on listen directive.
- Default server block handles unmatched requests.
- Without default_server, first server block on port is default.
- Useful for fallback or rejecting unknown hosts.

Full Transcript

When nginx receives a request, it looks at the Host header to find a matching server_name in its server blocks. If it finds a match, it uses that server block to process the request and send a response. If no server_name matches, nginx uses the server block marked with 'default_server' as a fallback. This ensures every request is handled. If no default_server is set, nginx uses the first server block listening on that port as the default. This behavior helps nginx decide how to respond to requests with unknown or missing hostnames.

Practice

1. What does the default_server directive do in an nginx configuration?

easy

A. It sets the server block to only respond to HTTPS requests.

B. It disables the server block from responding to any requests.

C. It redirects all requests to another server block.

D. It marks the server block to respond when no other server name matches the request.

Solution

1. Step 1: Understand the role of default_server

   The default_server directive in the listen line tells nginx which server block to use if no other server name matches the request.

2. Step 2: Analyze the options

   It marks the server block to respond when no other server name matches the request. correctly describes this behavior. Options A, B, and D describe unrelated or incorrect behaviors.

3. Final Answer:

   It marks the server block to respond when no other server name matches the request. -> Option D

4. Quick Check:

   default_server = marks fallback server [OK]

Hint: default_server means fallback server for unmatched requests [OK]

Common Mistakes:

• Thinking default_server disables the server
• Confusing default_server with HTTPS enforcement
• Assuming default_server redirects requests

2. Which of the following is the correct syntax to set a server block as the default server for HTTP on port 80?

easy

A. listen default_server 80;

B. listen 80 default_server;

C. default_server listen 80;

D. listen 80 default;

Solution

1. Step 1: Recall nginx listen directive syntax

   The correct syntax places the port number first, then the default_server flag: listen 80 default_server;.

2. Step 2: Evaluate each option

   listen 80 default_server; matches the correct syntax. Options A and C have incorrect order. listen 80 default; uses an invalid keyword default.

3. Final Answer:

   listen 80 default_server; -> Option B

4. Quick Check:

   listen port default_server order matters [OK]

Hint: Put port number before default_server in listen line [OK]

Common Mistakes:

• Swapping order of port and default_server
• Using invalid keywords like default instead of default_server
• Placing default_server outside listen directive

3. Given this nginx config snippet, what response will nginx serve for a request to IP address 192.168.1.10?

server {
    listen 80 default_server;
    server_name default.example.com;
    return 200 'Default Server';
}

server {
    listen 80;
    server_name site.example.com;
    return 200 'Site Server';
}

medium

A. Returns 'Default Server'

B. Returns 'Site Server'

C. Returns 404 Not Found

D. Returns 500 Internal Server Error

Solution

1. Step 1: Identify which server block matches the IP request

   The request is to IP 192.168.1.10, which does not match any server_name directive.

2. Step 2: Determine which server handles unmatched requests

   The server block with listen 80 default_server; handles requests without matching server_name, so it responds.

3. Final Answer:

   Returns 'Default Server' -> Option A

4. Quick Check:

   IP requests hit default_server block [OK]

Hint: Requests without matching server_name go to default_server [OK]

Common Mistakes:

• Assuming IP requests match any server_name
• Thinking unmatched requests return 404 automatically
• Confusing default_server with error handling

4. You configured two server blocks both with listen 80 default_server;. What will happen when nginx starts?

medium

A. nginx will fail to start due to conflicting default_server directives.

B. nginx will pick the first default_server block and ignore the second.

C. nginx will load both and round-robin requests between them.

D. nginx will merge both server blocks into one.

Solution

1. Step 1: Understand default_server uniqueness

   Only one server block per IP:port can be marked as default_server. Multiple default_server flags on same port cause conflict.

2. Step 2: Check nginx behavior on conflict

   nginx detects this conflict and refuses to start, showing an error about duplicate default_server.

3. Final Answer:

   nginx will fail to start due to conflicting default_server directives. -> Option A

4. Quick Check:

   Only one default_server per port allowed [OK]

Hint: Only one default_server per port; duplicates cause startup error [OK]

Common Mistakes:

• Thinking nginx picks one silently
• Assuming nginx load balances default_server blocks
• Believing nginx merges server blocks automatically

5. You want nginx to serve a custom page for all requests that do not match any server_name, including requests by IP or unknown hostnames. How should you configure the default server block to achieve this?

hard

A. Use listen 80 default_server; and set server_name localhost;.

B. Use listen 80; without default_server and set server_name _;.

C. Use listen 80 default_server; and set server_name _; with a custom return or root directive.

D. Use listen 80 default_server; and omit server_name entirely.

Solution

1. Step 1: Mark the server block as default_server

   To catch unmatched requests, the server block must have listen 80 default_server;.

2. Step 2: Use server_name _; as a wildcard

   Setting server_name _; is a common convention to match any hostname not matched elsewhere.

3. Step 3: Configure custom response

   Inside this block, use return or root to serve the custom page.

4. Final Answer:

   Use listen 80 default_server; and set server_name _; with a custom return or root directive. -> Option C

5. Quick Check:

   default_server + server_name _ = catch-all server [OK]

Hint: default_server plus server_name _ catches all unmatched requests [OK]

Common Mistakes:

• Not using default_server flag
• Omitting server_name or using localhost only
• Assuming default_server alone matches all hostnames