Try_files directive in Nginx - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to use try_files to check for the requested file or fallback to index.html.

Nginx

try_files $uri [1];

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

A$uri/ /index.html;

B$uri/ /index.html

C$uri/ /index.htm

D$uri /index.html

Attempts:

3 left

💡 Hint

Common Mistakes

Adding a semicolon inside the try_files argument

Using incorrect fallback file name

Missing spaces between file paths

The try_files directive checks if $uri or $uri/ exists, then falls back to /index.html.

2fill in blank

medium

Complete the code to try the requested URI, then the URI with a trailing slash, then fallback to /index.php.

Nginx

try_files $uri [1] /index.php;

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

A$uri/

B$uri//

C$uri/index.php

D$uri/index.html

Attempts:

3 left

💡 Hint

Common Mistakes

Using double slashes which is invalid

Trying a file instead of a directory for the second option

The directive tries $uri, then $uri/, then falls back to /index.php.

3fill in blank

hard

Fix the error in the try_files directive to properly fallback to /404.html if files are not found.

Nginx

try_files $uri $uri/ [1];

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

A/404.html

B404.html

C/404

D404

Attempts:

3 left

💡 Hint

Common Mistakes

Using relative path without leading slash

Using just status code instead of file path

The fallback file must be an absolute path starting with a slash, so /404.html is correct.

4fill in blank

hard

Fill both blanks to try the requested URI, then the URI with index.html, then fallback to /fallback.html.

Nginx

try_files [1] [2] /fallback.html;

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

A$uri

B$uri/index.html

C$uri/

D/index.html

Attempts:

3 left

💡 Hint

Common Mistakes

Using $uri/ instead of $uri/index.html

Missing leading slash in fallback

The directive tries $uri, then $uri/index.html, then falls back to /fallback.html.

5fill in blank

hard

Fill all three blanks to try the URI, then URI with trailing slash, then URI with index.php, falling back to /default.php.

Nginx

try_files [1] [2] [3] /default.php;

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

A$uri

B$uri/

C$uri/index.php

D/index.php

Attempts:

3 left

💡 Hint

Common Mistakes

Using absolute path in the second or third try

Missing trailing slash in second try

The directive tries $uri, then $uri/, then $uri/index.php, then falls back to /default.php.

Practice

1. What is the main purpose of the try_files directive in nginx?

easy

A. To check multiple files or paths in order and serve the first found

B. To restart the nginx server automatically

C. To define user permissions for files

D. To log errors in a custom file

Solution

1. Step 1: Understand the role of try_files

   The try_files directive checks a list of files or paths one by one.

2. Step 2: Identify its purpose

   It serves the first file found or falls back to a default if none exist.

3. Final Answer:

   To check multiple files or paths in order and serve the first found -> Option A

4. Quick Check:

   try_files = check files in order [OK]

Hint: Remember: try_files tries files one by one until success [OK]

Common Mistakes:

• Thinking try_files restarts nginx
• Confusing try_files with permission settings
• Assuming try_files logs errors

2. Which of the following is the correct syntax for the try_files directive in nginx?

easy

A. try_files file1 file2 fallback;

B. try_files file1 file2 =404;

C. try_files file1, file2, fallback;

D. try_files (file1 file2 fallback);

Solution

1. Step 1: Recall try_files syntax rules

   The try_files directive lists files separated by spaces, ending with a fallback like =404.

2. Step 2: Identify correct syntax

   try_files file1 file2 =404; uses spaces and ends with =404, which is valid syntax.

3. Final Answer:

   try_files file1 file2 =404; -> Option B

4. Quick Check:

   try_files syntax uses spaces and fallback [OK]

Hint: Use spaces, no commas or parentheses, end with fallback [OK]

Common Mistakes:

• Using commas between file names
• Adding parentheses around files
• Omitting fallback or using wrong fallback syntax

3. Given this nginx config snippet:

location / {
  try_files $uri $uri/ /index.html;
}

What happens when a user requests /about and /about is not a file but /about/ is a directory?

medium

A. nginx serves the /about file

B. nginx returns a 404 error

C. nginx serves the /about/ directory index

D. nginx serves /index.html fallback

Solution

1. Step 1: Understand try_files order

   nginx first checks if /about file exists, then /about/ directory.

2. Step 2: Apply to given request

   /about file is missing, but /about/ directory exists, so nginx serves the directory index.

3. Final Answer:

   nginx serves the /about/ directory index -> Option C

4. Quick Check:

   try_files checks files then directories [OK]

Hint: try_files checks files then directories in order [OK]

Common Mistakes:

• Assuming it serves /index.html fallback immediately
• Thinking it returns 404 if file missing
• Ignoring directory check after file check

4. Identify the error in this nginx config snippet:

location / {
  try_files $uri, $uri/, /fallback.html;
}

medium

A. Using commas between file names is invalid syntax

B. Missing semicolon at the end of try_files

C. Fallback file must be =404, not /fallback.html

D. Variables like $uri cannot be used in try_files

Solution

1. Step 1: Check try_files syntax

   try_files expects file names separated by spaces, not commas.

2. Step 2: Identify error in snippet

   The commas after $uri and $uri/ cause syntax error.

3. Final Answer:

   Using commas between file names is invalid syntax -> Option A

4. Quick Check:

   try_files uses spaces, no commas [OK]

Hint: No commas in try_files list, only spaces [OK]

Common Mistakes:

• Adding commas between file names
• Confusing fallback with error codes
• Thinking variables are disallowed in try_files

5. You want nginx to try serving /images/$uri, then /images/default.png if the first doesn't exist. Which try_files directive correctly implements this?

hard

A. try_files /images/$uri /images/default.png /index.html;

B. try_files $uri /images/default.png;

C. try_files /images/$uri /images/default.png=404;

D. try_files /images/$uri /images/default.png;

Solution

1. Step 1: Understand file paths in try_files

   To check /images/$uri first, it must be the first argument.

2. Step 2: Choose fallback file

   If the first file is missing, serve /images/default.png as fallback.

3. Step 3: Validate options

   try_files /images/$uri /images/default.png; matches this logic exactly without extra fallbacks or error codes.

4. Final Answer:

   try_files /images/$uri /images/default.png; -> Option D

5. Quick Check:

   try_files lists files in order, fallback last [OK]

Hint: List files in order, fallback last without extra codes [OK]

Common Mistakes:

• Using $uri without /images/ prefix
• Adding unnecessary fallback like =404
• Ending with unrelated fallback like /index.html