Request/response transformation in Nginx - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set a custom header in the response.

Nginx

add_header X-Custom-Header [1];

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

A"MyValue"

BMyValue

C'MyValue'

DMyValue;

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to quote the header value causes syntax errors.

Using single quotes instead of double quotes may not work as expected.

The add_header directive requires the header value to be quoted as a string.

2fill in blank

medium

Complete the code to rewrite the request URI to /newpath.

Nginx

rewrite ^[1] /newpath break;

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

A^/oldpath$

B/oldpath

C/oldpath$

D^/oldpath

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting anchors causes partial matches.

Using plain strings instead of regex patterns.

The rewrite directive uses a regular expression, so the pattern must start with ^ and end with $ to match exactly.

3fill in blank

hard

Fix the error in the proxy_set_header directive to forward the original Host header.

Nginx

proxy_set_header Host [1];

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

AHOST

B$host

C$Host

Dhost

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting the dollar sign causes nginx to treat it as a literal string.

Using incorrect capitalization of variables.

The variable $host holds the original Host header value and must be prefixed with $ to be interpreted correctly.

4fill in blank

hard

Fill both blanks to set a response header only if the status is 404.

Nginx

if ($status [1] 404) {
    add_header X-Error [2];
}

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

A==

B!=

C"Not Found"

D"Error"

Attempts:

3 left

💡 Hint

Common Mistakes

Using != instead of == reverses the condition.

Not quoting the header value causes syntax errors.

The if condition checks if the status equals 404 using ==. The header value should be a quoted string.

5fill in blank

hard

Fill all three blanks to create a map that transforms status codes to messages.

Nginx

map $status $message {
    200 [1];
    404 [2];
    default [3];
}

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

A"OK"

B"Not Found"

C"Unknown"

D"Error"

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the messages causes errors.

Using incorrect keys or missing the default case.

The map directive assigns messages to status codes. Each message must be a quoted string.