Preferential prefix match (^~) in Nginx - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a location block that uses preferential prefix match.

Nginx

location [1] /images/ {
    root /data;
}

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

A~

B^~

C~*

D=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '~' which is for regex match.

Using '=' which is for exact match.

Using '~*' which is case-insensitive regex match.

The ^~ prefix tells nginx to use this location if the request URI starts with the specified prefix, skipping regex checks.

2fill in blank

medium

Complete the code to ensure nginx uses the preferential prefix match for /static/ requests.

Nginx

location [1] /static/ {
    alias /var/www/static/;
}

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

A^~

B~

C=

D~*

Attempts:

3 left

💡 Hint

Common Mistakes

Using '~' or '~*' which are regex matches.

Using '=' which is for exact matches.

The ^~ prefix ensures nginx uses this location for URIs starting with /static/ without checking regex locations.

3fill in blank

hard

Fix the error in the location block to use preferential prefix match correctly.

Nginx

location [1] /api/ {
    proxy_pass http://backend;
}

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

A^~

B~

C=

D~*

Attempts:

3 left

💡 Hint

Common Mistakes

Using '~' or '~*' which are regex matches and do not guarantee prefix priority.

Using '=' which is for exact matches.

Using ^~ ensures nginx matches the prefix /api/ preferentially, skipping regex checks.

4fill in blank

hard

Fill both blanks to create a preferential prefix match location and a regex location.

Nginx

location [1] /downloads/ {
    root /data/downloads;
}

location [2] \.php$ {
    fastcgi_pass unix:/var/run/php.sock;
}

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

A^~

B~

C=

D~*

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the prefixes causing wrong matching behavior.

Using '=' for regex location.

The first location uses ^~ for preferential prefix match on /downloads/. The second uses ~ for regex matching PHP files.

5fill in blank

hard

Fill all three blanks to create a dictionary of locations with preferential prefix match and regex match conditions.

Nginx

server {
    listen 80;

    location [1] /media/ {
        root /var/media;
    }

    location [2] \.jpg$ {
        expires 30d;
    }

    location [3] /favicon.ico {
        log_not_found off;
    }
}

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

A^~

B~

C=

D~*

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up regex and prefix match prefixes.

Using '~*' instead of '~' for case-sensitive regex.

The ^~ prefix is for preferential prefix match on /media/. The ~ prefix is for regex matching .jpg files. The = prefix is for exact match on /favicon.ico.