Media info query gives 404 even though the file does exist

[DeathByDenim]

Component
Specs (BLE, HTTP)

Describe the bug
The media/list query lists all of the files but querying media/info for some of those files results in a 404.

To Reproduce
Steps to reproduce the behavior:

1. Run the list query: curl --request GET --url http://172.21.119.51:8080/gopro/media/list
2. Observe output: {"id":"1394424761222939043","media":[{"d":"100GOPRO","fs":[{"n":"GX020163.MP4","cre":"1768816698","mod":"1768816698","glrv":"238663283","ls":"-1","s":"6876755404"},{"n":"GX010164.MP4","cre":"1768839442","mod":"1768839442","glrv":"398932276","ls":"-1","s":"11536686945"},{"n":"GX020164.MP4","cre":"1768840467","mod":"1768840467","glrv":"218217997","ls":"-1","s":"6352656620"}]}]}
3. Attempt to get info of a file: curl --request GET --url http://172.21.119.51:8080/gopro/media/info\?path\=100GOPRO/GX020163.MP4
4. See 404 being returned

Expected behavior
The media info query should return JSON data with information about the file.

Logs

 ✘ jarno@goat  ~/data/GoPro  curl --request GET --url http://172.21.119.51:8080/gopro/media/list -v
Note: Unnecessary use of -X or --request, GET is already inferred.
*   Trying 172.21.119.51:8080...
* Established connection to 172.21.119.51 (172.21.119.51 port 8080) from 172.21.119.56 port 48172 
* using HTTP/1.x
> GET /gopro/media/list HTTP/1.1
> Host: 172.21.119.51:8080
> User-Agent: curl/8.18.0
> Accept: */*
> 
* Request completely sent off
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 379
< 
{"id":"1394424761222939043","media":[{"d":"100GOPRO","fs":[{"n":"GX020163.MP4","cre":"1768816698","mod":"1768816698","glrv":"238663283","ls":"-1","s":"6876755404"},{"n":"GX010164.MP4","cre":"1768839442","mod":"1768839442","glrv":"398932276","ls":"-1","s":"11536686945"},{"n":"GX020164.MP4","cre":"1768840467","mod":"1768840467","glrv":"218217997","ls":"-1","s":"6352656620"}]}]}
* Connection #0 to host 172.21.119.51:8080 left intact
 jarno@goat  ~/data/GoPro  curl --request GET --url http://172.21.119.51:8080/gopro/media/info\?path\=100GOPRO/GX020163.MP4 -v
Note: Unnecessary use of -X or --request, GET is already inferred.
*   Trying 172.21.119.51:8080...
* Established connection to 172.21.119.51 (172.21.119.51 port 8080) from 172.21.119.56 port 48178 
* using HTTP/1.x
> GET /gopro/media/info?path=100GOPRO/GX020163.MP4 HTTP/1.1
> Host: 172.21.119.51:8080
> User-Agent: curl/8.18.0
> Accept: */*
> 
* Request completely sent off
< HTTP/1.1 404 
< Content-Type: application/json
< Content-Length: 0
< 
* Connection #0 to host 172.21.119.51:8080 left intact

Screenshots
N/A

Hardware

• Camera: Hero12
• Linux terminal (Arch Linux)

Additional context
N/A

[DeathByDenim]

Actually, extra observation. I think this maybe always happens for part two of a video that has been split due to its length. That is, it seems to fail on GX02XXXX.MP4.