404 redirects with hugo server fail in multilingual mode on Windows

[jmooring]

structure

config/
├── _default/
│   └── config.toml
└── development/
    └── server.toml
content/
├── en/
│   └── _index.md
└── es/
    └── _index.md
layouts/
├── _default/
│   ├── baseof.html
│   ├── home.html
│   ├── list.html
│   └── single.html
└── 404.html

config\_default\config.toml

baseURL = 'https://example.org/'
title = 'Hugo Forum Topic #40568'

defaultContentLanguageInSubdir = true

[languages.en]
contentDir = 'content/en'
languageCode = 'en-US'
languageName = 'English'
weight = 1

[languages.es]
contentDir = 'content/es'
languageCode = 'es-ES'
languageName = 'Espanol'
weight = 2

config\development\server.toml

[[redirects]]
from = '/en/**'
to = '/en/404.html'
status = 404

[[redirects]]
from = '/es/**'
to = '/es/404.html'
status = 404

---

See:
https://github.com/gohugoio/hugo/blob/master/commands/server.go#L439

I suspect that this:

file, err := fs.Open(filepath.FromSlash(strings.TrimPrefix(redirect.To, u.Path)))

Should be this:

file, err := fs.Open(strings.TrimPrefix(redirect.To, u.Path))

---

MRE:

git clone --single-branch -b hugo-forum-topic-40568 https://github.com/jmooring/hugo-testing hugo-forum-topic-40568
cd hugo-forum-topic-40568
hugo server

Reference:
https://discourse.gohugo.io/t/404-pages-on-localhost-for-multilingual-site-failing/40568/15

[bep]

file, err := fs.Open(filepath.FromSlash(strings.TrimPrefix(redirect.To, u.Path)))

I doubt that that is the culprit.

[jmooring]

I doubt that that is the culprit.

The err value is "http: invalid character in file path"

[bep]

The err value is "http: invalid character in file path"

I will boot up my Windows VM and have a look tomorrow ... It's Windows 8 and every time i boot it I get a million update notifications.

[bep]

The err value is "http: invalid character in file path"

Yea, right, I misread what file system we're reading here, you were right about the "culprit" :-)

[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.