Index directive in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the index directive in nginx?

The index directive tells nginx which file to serve when a directory is requested. It looks for the specified files in order and serves the first one it finds.

beginner

How does nginx behave if the index directive is not set and a directory is requested?

If the index directive is not set, nginx uses the default value index.html and attempts to serve that file for a directory request. If the file does not exist, it may return a 403 Forbidden error or list the directory contents if autoindex is enabled.

beginner

Example: <br> index index.html index.htm; <br> What does this configuration mean?

This means nginx will first look for a file named index.html in the requested directory. If it is not found, it will look for index.htm. It serves the first file found.

intermediate

Can the index directive accept multiple file names? How does nginx use them?

Yes, the index directive can list multiple file names separated by spaces. Nginx checks them in order and serves the first existing file it finds in the directory.

intermediate

Where in the nginx configuration file can the index directive be placed?

The index directive can be placed inside the http, server, or location blocks to control default files at different levels.

What does the nginx index directive do?

A Specifies default files to serve when a directory is requested

B Defines the server's IP address

C Sets the maximum file upload size

D Configures SSL certificates

The index directive tells nginx which file to serve by default when a directory URL is requested.

If index index.html index.htm; is set, and both files exist, which one will nginx serve?

A index.htm

B Both files simultaneously

C index.html

D It will return an error

Nginx serves the first file listed in the index directive that exists. Here, index.html is first.

Where can the index directive be used in nginx configuration?

A Only inside <code>server</code> block

B Inside <code>http</code>, <code>server</code>, or <code>location</code> blocks

C Only inside <code>http</code> block

D Only inside <code>location</code> block

The index directive can be placed in http, server, or location blocks to control default files at different levels.

What happens if no file listed in the index directive exists in the directory?

A Nginx lists the directory contents if autoindex is enabled

B Nginx serves the first file anyway

C Nginx serves a 404 Not Found error

D Nginx restarts automatically

If no index file is found, nginx may list directory contents if autoindex is enabled; otherwise, it may return an error.

Can the index directive accept only one file name?

A No, it requires at least two file names

B Yes, but only if the file is named index.html

C No, it only accepts directories

D Yes, it can accept one or more file names

The index directive can accept one or multiple file names to check in order.

Explain how the nginx index directive works when a user requests a directory URL.

Think about what nginx does when you visit a folder on a website.

Describe where you can place the index directive in nginx configuration and why placement matters.

Consider different levels of configuration in nginx.