Unexpected behavior when using `%2F` (`/`) in URIs (FileSystem Resource)

Assume you have a file stored at FileSystem/sample_image_uploads/U5497/00E_0/20221121_122842.jpg. As expected, a GET request to https://localhost:10443/FileSystem/sample_image_uploads/U5497/00E_0/20221121_122842.jpg downloads the file 20221121_122842.jpg.

A GET request to https://localhost:10443/FileSystem/sample_image_uploads%2FU5497%2F00E_0%2F20221121_122842.jpg, however, downloads the same file, but with the file name sample_image_uploads_U5497_00E_0_20221121_122842.jpg.

Two things are wrong here:

The file name
The server shouldn't resolve the escaped /, i.e., the %2F in the first place and return a 404 instead.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information