MIME types configuration in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Identify MIME type served by Nginx

Given the following Nginx configuration snippet, what MIME type will Nginx serve for a file named example.svg?

Nginx

types {
    text/html  html;
    image/svg+xml  svg;
    application/javascript  js;
}

location / {
    root /var/www/html;
}

A application/octet-stream

B text/html

C application/javascript

D image/svg+xml

💡 Hint

Check the MIME type associated with the .svg extension in the types block.

The configuration maps the .svg extension to the MIME type image/svg+xml, so Nginx will serve example.svg with that MIME type.

❓ Configuration

intermediate

Correct MIME type for JSON files

Which configuration snippet correctly sets the MIME type for files with the .json extension to application/json in Nginx?

A

types {
    application/json json;
}

B

types {
    text/json json;
}

C

types {
    application/javascript json;
}

D

types {
    application/json js;
}

💡 Hint

The MIME type must be application/json and the extension json.

Option A correctly maps the .json extension to application/json. Other options either use wrong MIME types or wrong extensions.

❓ Troubleshoot

advanced

Why is Nginx serving wrong MIME type?

You configured Nginx to serve .woff2 files with MIME type font/woff2 but browsers still treat them as application/octet-stream. What is the most likely cause?

A The <code>mime.types</code> file is not included in the main configuration.

B The <code>types</code> block is missing the <code>woff2</code> extension mapping.

C The <code>default_type</code> directive is set to <code>application/octet-stream</code> and overrides types.

D The <code>root</code> directive is incorrect, causing files not to be found.

💡 Hint

Check if the standard MIME types file is loaded by Nginx.

If the mime.types file is not included, Nginx won't know the mapping for .woff2 and will use the default type application/octet-stream.

🔀 Workflow

advanced

Order of MIME type resolution in Nginx

In what order does Nginx determine the MIME type for a requested file?

A Check <code>types</code> block in current context → Use <code>default_type</code> if no match → Check <code>mime.types</code> file

B Check <code>types</code> block in current context → Check <code>mime.types</code> file → Use <code>default_type</code> if no match

C Check <code>mime.types</code> file → Check <code>types</code> block in current context → Use <code>default_type</code> if no match

D Use <code>default_type</code> first → Check <code>types</code> block → Check <code>mime.types</code> file

💡 Hint

Nginx first looks at local types, then global mime.types, then default.

Nginx first checks the types defined in the current context, then the global mime.types file, and finally falls back to default_type if no match is found.

✅ Best Practice

expert

Best practice for custom MIME types in Nginx

What is the best practice to add a custom MIME type for a new file extension .abc without modifying the default mime.types file?

A Add a <code>types</code> block with the new mapping inside the <code>http</code> block in your main config.

B Directly edit the <code>mime.types</code> file to add the new extension and reload Nginx.

C Create a separate file with the new MIME type and include it in the main config using the <code>include</code> directive.

D Use the <code>default_type</code> directive to set the MIME type for .abc files.

💡 Hint

Avoid editing default files; use includes for customizations.

Best practice is to create a separate file with custom MIME types and include it in the main config. This keeps default files intact and makes upgrades easier.

Practice

1. What is the main purpose of configuring MIME types in nginx?

easy

A. To tell browsers how to handle different file types

B. To set the server's IP address

C. To define user access permissions

D. To configure server logging format

Solution

1. Step 1: Understand MIME types role

   MIME types tell browsers what kind of content is being sent, so they can handle it properly.

2. Step 2: Relate to nginx configuration

   In nginx, configuring MIME types maps file extensions to content types for correct browser handling.

3. Final Answer:

   To tell browsers how to handle different file types -> Option A

4. Quick Check:

   MIME types = browser file handling [OK]

Hint: MIME types = file type instructions for browsers [OK]

Common Mistakes:

• Confusing MIME types with server IP settings
• Thinking MIME types control user permissions
• Mixing MIME types with logging configuration

2. Which of the following is the correct syntax to define MIME types in nginx configuration?

easy

A. mime_types { html text/html; css text/css; }

B. types { .html text/html; .css text/css; }

C. types { html: text/html; css: text/css; }

D. mime { .html = text/html; .css = text/css; }

Solution

1. Step 1: Recall nginx MIME types syntax

   The correct block is types { .ext mime/type; } with semicolons and dot before extension.

2. Step 2: Compare options

   types { .html text/html; .css text/css; } matches correct syntax with types { .html text/html; .css text/css; }.

3. Final Answer:

   types { .html text/html; .css text/css; } -> Option B

4. Quick Check:

   Correct syntax uses 'types' block with dot extensions [OK]

Hint: Use 'types { .ext mime/type; }' with dots and semicolons [OK]

Common Mistakes:

• Omitting dots before file extensions
• Using colons or equals instead of spaces
• Wrong block name like 'mime_types' or 'mime'

3. Given this nginx config snippet:

types {
  .json application/json;
  .xml application/xml;
}

What MIME type will nginx send for a file named data.json?

medium

A. application/json

B. text/plain

C. application/xml

D. text/html

Solution

1. Step 1: Check the file extension

   The file is named data.json, so the extension is .json.

2. Step 2: Match extension to MIME type in config

   The config maps .json to application/json.

3. Final Answer:

   application/json -> Option A

4. Quick Check:

   .json = application/json [OK]

Hint: Match file extension to MIME type in 'types' block [OK]

Common Mistakes:

• Confusing .json with .xml MIME type
• Assuming default text/plain without config
• Ignoring the dot before extension

4. You added this to your nginx config:

types {
  .txt text/plain
  .md text/markdown;
}

Why might nginx fail to start?

medium

A. MIME types cannot include 'text/markdown'

B. Wrong block name 'types' instead of 'mime_types'

C. File extensions must not have dots

D. Missing semicolon after .txt MIME type

Solution

1. Step 1: Check syntax for each MIME type line

   Each line must end with a semicolon; the line for .txt is missing it.

2. Step 2: Validate block name and extensions

   The block name types is correct, and dots before extensions are required.

3. Final Answer:

   Missing semicolon after .txt MIME type -> Option D

4. Quick Check:

   Every MIME type line ends with semicolon [OK]

Hint: Check semicolons after each MIME type line [OK]

Common Mistakes:

• Forgetting semicolon at line end
• Changing 'types' block name incorrectly
• Removing dots before extensions

5. You want nginx to serve a new file type .abc with MIME type application/x-abc. Which config snippet correctly adds this without removing existing types?

hard

A. mime_types { .abc application/x-abc; }

B. types { .abc application/x-abc; }

C. types { include mime.types; .abc application/x-abc; }

D. types { .abc = application/x-abc; }

Solution

1. Step 1: Preserve existing MIME types

   To keep existing types, include the default mime.types file inside the types block.

2. Step 2: Add new MIME type after include

   After including existing types, add .abc application/x-abc; to extend the list.

3. Final Answer:

   types { include mime.types; .abc application/x-abc; } -> Option C

4. Quick Check:

   Include existing types then add new ones [OK]

Hint: Include mime.types before adding new MIME types [OK]

Common Mistakes:

• Overwriting existing types by not including mime.types
• Using wrong block name 'mime_types'
• Using equals sign instead of space