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.