MIME types configuration in Nginx - Step-by-Step Execution

Process Flow - MIME types configuration

Client requests file

↓

Nginx receives request

↓

Check file extension

↓

Look up MIME type in mime.types

↓

Set Content-Type header

↓

Send response with correct MIME type

Nginx checks the requested file's extension, finds the matching MIME type from its configuration, sets the Content-Type header, and sends the response.

Execution Sample

Nginx

location / {
    root /var/www/html;
    include mime.types;
    default_type application/octet-stream;
}

This config snippet tells nginx to serve files from /var/www/html, use mime.types to find MIME types, and use a default if none matches.

Process Table

Step	Action	File Requested	File Extension	MIME Type Found	Content-Type Header Set
1	Receive request	/index.html	.html	text/html	text/html
2	Receive request	/image.png	.png	image/png	image/png
3	Receive request	/script.js	.js	application/javascript	application/javascript
4	Receive request	/unknownfile.xyz	.xyz	none	application/octet-stream
5	Receive request	/style.css	.css	text/css	text/css

💡 All requests processed by matching extension to MIME type or using default if none found.

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5
Requested File		/index.html	/image.png	/script.js	/unknownfile.xyz	/style.css
File Extension		.html	.png	.js	.xyz	.css
MIME Type		text/html	image/png	application/javascript	none	text/css
Content-Type Header		text/html	image/png	application/javascript	application/octet-stream	text/css

Key Moments - 2 Insights

Why does nginx use 'application/octet-stream' for unknown file extensions?

When the file extension is not found in mime.types (see step 4 in execution_table), nginx uses the default_type as a fallback to ensure the file is served with a safe generic MIME type.

How does nginx determine the MIME type for a requested file?

Nginx extracts the file extension from the requested file (execution_table column 'File Extension'), then looks it up in the mime.types file to find the matching MIME type.

Visual Quiz - 3 Questions

Look at the execution_table, what Content-Type header is set for '/script.js'?

A text/javascript

B application/javascript

C application/json

D text/plain

💡 Hint

Check the row where File Requested is '/script.js' and see the Content-Type Header column.

At which step does nginx use the default MIME type 'application/octet-stream'?

A Step 4

B Step 2

C Step 1

D Step 5

💡 Hint

Look for the step where MIME Type Found is 'none' and Content-Type Header is 'application/octet-stream'.

If a new file type '.md' with MIME 'text/markdown' is added to mime.types, what changes in the execution_table?

A All '.html' files would be served as 'text/markdown'

B The default_type would change to 'text/markdown'

C A new row with '.md' extension and 'text/markdown' MIME type would appear

D No change unless nginx is restarted

💡 Hint

Adding a MIME type allows nginx to match new extensions and set correct Content-Type headers as shown in the execution_table rows.

Concept Snapshot

MIME types config in nginx:
- Use 'include mime.types;' to load types
- Match file extension to MIME type
- Set 'default_type' for unknown extensions
- Content-Type header tells browser file type
- Ensures correct file handling by clients

Full Transcript

When a client requests a file, nginx checks the file extension. It looks up this extension in the mime.types file to find the matching MIME type. If found, nginx sets the Content-Type header to that MIME type. If not found, it uses the default_type, usually 'application/octet-stream'. This header helps browsers know how to handle the file. The example shows requests for various files and how nginx sets the Content-Type accordingly.