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

Process Flow - Default type handling

Client Request

↓

Check file extension

↓

Match MIME type in types block?

No→Use default_type

Yes↓

Set Content-Type header

↓

Send Response

Nginx checks the requested file's extension to find a matching MIME type. If none is found, it uses the default_type to set the Content-Type header.

Execution Sample

Nginx

location / {
    types {
        text/html html;
        image/png png;
    }
    default_type application/octet-stream;
}

This config sets MIME types for .html and .png files and uses application/octet-stream as the default Content-Type if no match is found.

Process Table

Step	Requested File	Extension	MIME Type Found?	Content-Type Set	Action
1	/index.html	html	Yes	text/html	Serve with text/html
2	/image.png	png	Yes	image/png	Serve with image/png
3	/file.unknown	unknown	No	application/octet-stream	Serve with default_type
4	/noextension		No	application/octet-stream	Serve with default_type

💡 Requests without matching extension use default_type for Content-Type header.

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4
Content-Type	unset	text/html	image/png	application/octet-stream	application/octet-stream

Key Moments - 2 Insights

Why does nginx use application/octet-stream for some files?

When the file extension is not listed in the types block (see execution_table rows 3 and 4), nginx uses the default_type value to set the Content-Type header.

What happens if a requested file has no extension?

Nginx cannot find a matching MIME type, so it uses default_type as shown in execution_table row 4.

Visual Quiz - 3 Questions

Look at the execution table, what Content-Type is set for /image.png?

A text/html

B image/png

C application/octet-stream

D unknown

💡 Hint

Check execution_table row 2 under Content-Type Set column.

At which step does nginx use the default_type for Content-Type?

A Step 1

B Step 2

C Step 3

D None

💡 Hint

Look at execution_table rows where MIME Type Found? is No.

If you add 'application/json json;' to types, what Content-Type will /data.json get?

A application/json

B application/octet-stream

C text/html

D image/png

💡 Hint

Adding a type for .json means nginx finds a MIME type instead of using default_type.

Concept Snapshot

Nginx uses the 'types' block to map file extensions to MIME types.
If no match is found, it uses 'default_type' to set Content-Type.
This ensures every response has a Content-Type header.
Example: default_type application/octet-stream;
Files without known extensions get this default MIME type.

Full Transcript

Nginx handles file requests by checking the file extension against a list of known MIME types defined in the 'types' block. If it finds a match, it sets the Content-Type header accordingly. If no match is found, nginx uses the 'default_type' directive to set a fallback Content-Type header, usually 'application/octet-stream'. This process ensures that every response has a Content-Type header, which helps browsers understand how to handle the file. For example, a request for '/index.html' sets Content-Type to 'text/html', while a request for '/file.unknown' uses the default type. Files without extensions also use the default type. This behavior is important to configure correctly for proper content delivery.

Practice

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

easy

A. Sets the MIME type for files without a known extension

B. Defines the default server port

C. Specifies the default root directory

D. Enables gzip compression by default

Solution

1. Step 1: Understand the purpose of default_type

   The default_type directive tells nginx what MIME type to use when it cannot determine the file type from the extension.

2. Step 2: Match the directive to its function

   Since it sets the fallback MIME type, it helps browsers know how to handle unknown files.

3. Final Answer:

   Sets the MIME type for files without a known extension -> Option A

4. Quick Check:

   default_type sets fallback MIME type = A [OK]

Hint: default_type sets fallback MIME type for unknown files [OK]

Common Mistakes:

• Confusing default_type with server port settings
• Thinking it sets root directory
• Assuming it enables compression

2. Which of the following is the correct syntax to set the default MIME type to application/json inside an nginx http block?

easy

A. default_type 'application/json';

B. default_type application/json;

C. default_type: application/json;

D. default_type = application/json;

Solution

1. Step 1: Recall nginx directive syntax

   nginx directives use the format: directive_name value; without equals or colons.

2. Step 2: Identify the correct syntax for default_type

   The correct syntax is default_type application/json; with no quotes needed.

3. Final Answer:

   default_type application/json; -> Option B

4. Quick Check:

   Correct nginx directive syntax = D [OK]

Hint: nginx directives end with semicolon, no equals or colon [OK]

Common Mistakes:

• Using equals sign (=) in directive
• Adding colon (:) after directive
• Putting quotes around MIME type unnecessarily

3. Given this nginx config snippet inside a location block:

default_type text/plain;

What will be the Content-Type header for a request to a file named unknownfile.xyz?

medium

A. text/plain

B. application/octet-stream

C. application/json

D. text/html

Solution

1. Step 1: Identify the default_type setting

   The config sets default_type text/plain; inside the location block.

2. Step 2: Determine MIME type for unknown extension

   Since .xyz is unknown, nginx uses the default_type value text/plain as Content-Type.

3. Final Answer:

   text/plain -> Option A

4. Quick Check:

   Unknown file uses default_type = A [OK]

Hint: Unknown extensions get default_type MIME type [OK]

Common Mistakes:

• Assuming default is application/octet-stream
• Confusing with text/html default
• Ignoring location block override

4. You set default_type application/json; in your nginx server block, but requests to unknown file types still return text/html. What is the most likely cause?

medium

A. You forgot to reload nginx after changing config

B. The file extension is recognized, so default_type is ignored

C. default_type cannot be set in server block

D. Another default_type directive in a location block overrides it

Solution

1. Step 1: Understand nginx directive inheritance

   Directives in location blocks override those in server blocks.

2. Step 2: Identify override causing unexpected Content-Type

   If a location block sets default_type text/html;, it will override the server block setting.

3. Final Answer:

   Another default_type directive in a location block overrides it -> Option D

4. Quick Check:

   Location block overrides server block default_type = B [OK]

Hint: Location block default_type overrides server block [OK]

Common Mistakes:

• Thinking default_type can't be set in server block
• Forgetting to reload nginx
• Assuming file extension is always unknown

5. You want nginx to serve unknown file types as application/octet-stream globally, but for a specific /images location, serve unknown files as image/png. Which configuration correctly achieves this?

hard

A. Set default_type application/octet-stream; only in location /images

B. In server block: default_type image/png; and in location /images: default_type application/octet-stream;

C. In http block: default_type application/octet-stream; and in location /images: default_type image/png;

D. Set default_type image/png; only in http block

Solution

1. Step 1: Set global default_type in http block

   Setting default_type application/octet-stream; in http block applies globally to all requests.

2. Step 2: Override default_type in specific location

   Setting default_type image/png; inside location /images overrides the global setting for that path.

3. Final Answer:

   In http block: default_type application/octet-stream; and in location /images: default_type image/png; -> Option C

4. Quick Check:

   Global default_type overridden by location block = C [OK]

Hint: Set global default_type in http, override in location [OK]

Common Mistakes:

• Reversing global and location settings
• Setting default_type only in location without global
• Using server block instead of http for global