MIME types configuration in Nginx - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to include the MIME types file in the nginx configuration.

Nginx

include [1];

Drag options to blanks, or click blank then click option'

A/usr/local/nginx/mime.types

B/etc/nginx/conf.d/mime.types

C/etc/nginx/mime.conf

D/etc/nginx/mime.types

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong path like /etc/nginx/mime.conf which does not exist.

Forgetting to include the MIME types file, causing incorrect content types.

The standard location for the MIME types file in nginx is /etc/nginx/mime.types. Including this file allows nginx to map file extensions to MIME types correctly.

2fill in blank

medium

Complete the MIME type declaration for .json files in the mime.types file.

Nginx

application/[1] json;

Drag options to blanks, or click blank then click option'

Axml

Bjavascript

Cjson

Dplain

Attempts:

3 left

💡 Hint

Common Mistakes

Using application/javascript which is for .js files.

Confusing plain text with JSON MIME type.

The correct MIME type for JSON files is application/json which nginx uses for .json files.

3fill in blank

hard

Fix the error in the MIME type declaration for .html files.

Nginx

text/[1] html;

Drag options to blanks, or click blank then click option'

Ahtm

Bhtml

Cplain

Dxml

Attempts:

3 left

💡 Hint

Common Mistakes

Using htm instead of html causes mismatch.

Using plain or xml for HTML files.

The correct MIME type for HTML files is text/html. Using html completes the declaration properly.

4fill in blank

hard

Fill both blanks to define the MIME type for .css files correctly.

Nginx

[1]/[2] css;

Drag options to blanks, or click blank then click option'

Atext

Bapplication

Ccss

Dplain

Attempts:

3 left

💡 Hint

Common Mistakes

Using application/css which is incorrect.

Using plain/css which is invalid.

The correct MIME type for CSS files is text/css. So text and css fill the blanks properly.

5fill in blank

hard

Fill both blanks to create a MIME types map for .png and .jpg files.

Nginx

{BLANK_1}} { { image/png png; {{BLANK_2}} jpg; };

Drag options to blanks, or click blank then click option'

Atypes

B{

Cimage/png

Dimage/jpeg

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the braces or using wrong keywords.

Mixing up MIME types for png and jpg files.

The correct syntax to define MIME types in nginx is using the types block with curly braces. Inside, png maps to image/png and jpg maps to image/jpeg. Here, the blanks are filled with types, {, and image/jpeg respectively.

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