NGINX location block for subdirectory causing index page to return 404

rguttersohn

3/1/24, 6:18 PM

Just learning basic NGINX. I am trying to rewrite some clean URLS so they redirect to files in a subdirectory called on the server called views.

The below config accomplishes this. However, whenever I return to the index page, it returns a 404 error.

As you'll see below, I define my index as index.html. I assumed this would ensure that the index.html be treated as the index file. However, it appears NGINX is opting to use the first location block to determine the index. That makes sense because '/' is the index. However, I am attempting to only use that first location block for subsequent pages (ie nginx-practice.test/secondpage)

Here's the config file:

server {
    listen 127.0.0.1:80;
    server_name nginx-practice.test;
    root /usr/robertguttersohn/Sites/nginx-practice/public;

    index index.html;

    location ~ /. {
        root /user/Sites/nginx-practice/public/views;
        try_files $uri @htmlext =404;
    }

    location @htmlext {
        rewrite ^(.*)$ $1.html last;
    } 

    access_log /usr/local/var/log/nginx/access.log;
    error_log /usr/local/var/log/nginx/error.log;

}

How do I have NGINX use index.html for the index page and then use the rewrite for all subsequent pages?

453

1 + 1

nginx

Pothi Kalimuthu

3/3/24, 8:01 AM

You could use `location = / {}` to target index.html file just for the home page.

Score:1

Server

Pothi Kalimuthu

3/4/24, 3:11 AM

You could use location = / {} to target index.html file just for the home page and then use the generic location / {} block to target the subsequent pages. Here's an example...

server {
    listen 127.0.0.1:80;
    server_name nginx-practice.test;
    root /user/robertguttersohn/Sites/nginx-practice/public;

    index index.html;

    # To isolate home page
    location = / { try_files /index.html =404; }

    # To parse subsequent pages
    location / {
        root /user/robertguttersohn/Sites/nginx-practice/public/views;
        try_files $uri @url.html =404;
    }

    access_log /usr/local/var/log/nginx/access.log;
    error_log /usr/local/var/log/nginx/error.log;

}

As you can see, the location @htmlext {} block can be eliminated too.

In my example, I have used /user/robertguttersohn/Sites/nginx-practice/public as root directory and /user/robertguttersohn/Sites/nginx-practice/public/views as sub-directory. You may want to update it to fit your environment. Please remember to restart Nginx server after making any change in configuration.

For more info on how location works, please checkout https://nginx.org/r/location .

+ 0

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: NGINX location block for subdirectory causing index page to return 404

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.