Non-existent two-part path results with 404 page which doesn't load css and js files when using relativeURLs: true

[bugok]

What version of Hugo are you using (hugo version)?

0.124.1

Does this issue reproduce with the latest release?

I'm not sure. It's hard to reproduce locally.

More information

When accessing a two-level, non existent path of a website, css and js files don't load.

Accessing my website at https://www.noamlerner.com works great.
Accessing https://www.noamlerner.com/nonexistent results with a 404 with a page which can load the css and js files.
However, accessing https://www.noamlerner.com/nonexistent/another results with a 404 response, but css and js files can't load.

Looking at the developer tools console I see that the static content is trying to be retrieved from: https://www.noamlerner.com/nonexistent/. For example:

https://www.noamlerner.com/nonexistent/css/main.bundle.min.5ea5a2723a6600ec162c3206366e9a4fbb0c82f79711e724dea2dfe92a2a864f.css
https://www.noamlerner.com/nonexistent/site.webmanifest

For context, I am using the relativeURLs: true option in my hugo config. You can see in this discussion why: jpanther/congo#857.

Furthermore, I tried reproducing this with other random hugo websites I found, and got 3/3:

I searched github for websites which use relativeURLs: https://github.com/search?q=%22relativeURLs%3A+true%22+path%3A%2F%5Econfig%5C.yaml%2F&type=code

Examples:

• https://build.prestashop-project.org/prestashop-specs/ : https://github.com/PrestaShop/prestashop-specs/blob/master/config.yml#L6
• https://www.yopa.page/ : https://github.com/ypark9/yopa.page/blob/c5c9a0ae5c7f2ae9939423a7db066dbd6cbaa375/config.yaml#L2
• https://hackforprivacy.org/ : https://github.com/littlejuh/cryptohack.net/blob/master/config.yaml#L2

All of them showed with the same behavior - when loading the a two-part, non-existent path - the 404 page can't load static content.

[jmooring]

The path begins with ./, so it is relative to the current page. It is not relative to the directory from which the assets are served. There's no way that will work.

And there is almost never a good reason to enable relativeURLs:
https://gohugo.io/content-management/urls/#relative-urls

Do not enable this option unless you are creating a serverless site, navigable via the file system.

This is a support issue. Please create a new topic in the Hugo forum if you need additional assistance. Thanks.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.