[Bug]: Renaming exports fails with 404 error when new name contains a slash

[Zinurist]

Checklist

• I have updated to the latest available Frigate version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in incognito mode to rule out problems with any third party extensions or plugins I have installed.

Describe the problem you are having

Renaming an export to something that contains a slash results in a 404 error.
It's still possible to create exports with a slash in their name.

Steps to reproduce

1. Create an export named X
2. Rename export to X/Y
3. 404 error

Version

0.14.1-f4f3cfa

In which browser(s) are you experiencing the issue with?

No response

Frigate config file

not related

docker-compose file or Docker CLI command

I'm using the ghcr.io/blakeblackshear/frigate:0.14.1 image

Relevant Frigate log output

2025-01-01 15:16:32.174377454  172.18.0.1 - - [01/Jan/2025:15:16:32 +0100] "PATCH /api/export/cam1_305rte/X%2FY HTTP/1.1" 404 184 "https://<frigate instance>/export" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "192.168.0.62"

Relevant go2rtc log output

.

Operating system

Debian

Install method

Docker Compose

Network connection

Wired

Camera make and model

.

Screenshots of the Frigate UI's System metrics pages

.

Any other information that may be helpful

My frigate instance sits behind a nginx reverse proxy, but the same happens when I connect to frigate directly, so I don't think it's an issue with that (also, request url as seen in the browser matches the url in the logs). Maybe the nginx running in the frigate container is deencoding the url or something, idk.

Just my opinion: The new name should be part of a json body in the PATCH request instead of part of the URL

[NickM-27]

Thanks, created an issue for it #15765