Default type handling in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does NGINX determine the MIME type of a served file by default?

When NGINX serves a static file, how does it decide which MIME type to send in the Content-Type header if no explicit type is set?

A It uses the file extension and the <code>mime.types</code> file to map extensions to MIME types.

B It always sends <code>application/octet-stream</code> regardless of file type.

C It guesses the MIME type by reading the file content.

D It uses the <code>default_type</code> directive only and ignores file extensions.

💡 Hint

Think about how web servers usually identify file types for HTTP headers.

NGINX uses the file extension and the mime.types file to map extensions to MIME types. This allows it to send the correct Content-Type header for known file types.

💻 Command Output

intermediate

Output of NGINX with missing MIME type for .xyz files

Given this NGINX configuration snippet:

http {
    include       mime.types;
    default_type  application/octet-stream;
}
server {
    listen 8080;
    location / {
        root /usr/share/nginx/html;
    }
}

If a client requests file.xyz (an unknown extension), what Content-Type header will NGINX send?

A No Content-Type header is sent

B Content-Type: application/octet-stream

C Content-Type: application/xyz

D Content-Type: text/plain

💡 Hint

Consider what default_type is set to and what happens if the extension is unknown.

If the file extension is not found in mime.types, NGINX uses the default_type directive value, which here is application/octet-stream.

❓ Configuration

advanced

Correctly setting default MIME type for unknown files

You want NGINX to send text/plain as the default MIME type for files with unknown extensions. Which configuration snippet achieves this?

A

http {
    include mime.types;
    default_type text/plain;
}

B

http {
    default_type text/plain;
    include mime.types;
}

C

http {
    include mime.types;
    default_type application/octet-stream;
    default_type text/plain;
}

D

http {
    include mime.types;
    default_type;
}

💡 Hint

The order of directives matters and default_type must have a valid value.

Setting default_type text/plain; after including mime.types correctly sets the default MIME type for unknown extensions.

❓ Troubleshoot

advanced

Why is NGINX sending 'Content-Type: text/html' for all files?

An NGINX server is sending Content-Type: text/html for every file, including images and CSS. The config includes include mime.types; and default_type application/octet-stream;. What is the most likely cause?

A The <code>root</code> directive is missing, causing NGINX to default to <code>text/html</code>.

B The <code>default_type</code> directive is ignored if <code>include mime.types;</code> is present.

C NGINX caches MIME types and needs a restart to apply changes.

D The <code>mime.types</code> file is missing or empty, so NGINX falls back to <code>default_type</code> which is overridden elsewhere.

💡 Hint

Think about what happens if the MIME types file is not loaded properly.

If the mime.types file is missing or empty, NGINX falls back to default_type (application/octet-stream). Since text/html is being sent instead, default_type must be overridden elsewhere (e.g., in server or location context).

🔀 Workflow

expert

Order of directives affecting MIME type handling

Consider this NGINX http block:

http {
    default_type application/json;
    include mime.types;
}

What MIME type will NGINX send for a .css file request?

A application/json

B application/octet-stream

C text/css

D No Content-Type header

💡 Hint

NGINX prioritizes MIME type lookup from the types map (mime.types) before using default_type.

NGINX looks up the file extension in the MIME types map from mime.types. The .css extension maps to text/css, so that is used. The default_type directive is only for unmatched extensions, and directive order does not affect known mappings.