Bad Request returned from API when editing a path published by software.

[WCEarp]

Which version are you using?

v0.23.7

Which operating system are you using?

• Linux amd64 standard
• Linux amd64 Docker
• Linux arm64 standard
• Linux arm64 Docker
• Linux arm7 standard
• Linux arm7 Docker
• Linux arm6 standard
• Linux arm6 Docker
• Windows amd64 standard
• Windows amd64 Docker (WSL backend)
• macOS amd64 standard
• macOS amd64 Docker
• Other (please describe)

Describe the issue

API returns a 400 Bad Request when attempting to edit a path that was added by software, e.g. Gstreamer. The issue does not appear to exist when editing a path that was added via the API or manually entered into the config file.

Describe how to replicate the issue

1. Start the server
2. Publish with a Gstreamer command: gst-launch-1.0 videotestsrc ! x264enc ! rtspclientsink location=rtsp://{API_ADDRESS}:{RTSP_PORT}/test
3. From a terminal, use curl edit the path's config: curl -X POST http://{API_ADDRESS}:{API_PORT}/v2/config/paths/edit/test -H 'Content-Type: application/json' -d '{"runOnInitRestart": true}'
4. MediaMTX return's 400 Bad Request

Did you attach the server logs?

yes
mediamtx_v0.23.7_issue2067.log

Did you attach a network dump?

no

[aler9]

Hello, publishing to a path doesn't cause a path configuration to be created, on the contrary, publishing to a path is only possible if a path configuration already exists. The default configuration is something like that:

paths:
  all:

The path configuration called "all" catches all paths. If you want to create and control a configuration for a certain path, add it through the configuration file or through the API:

paths:
  test:

[WCEarp]

Hello, publishing to a path doesn't cause a path configuration to be created, on the contrary, publishing to a path is only possible if a path configuration already exists. The default configuration is something like that:

paths:
  all:

The path configuration called "all" catches all paths. If you want to create and control a configuration for a certain path, add it through the configuration file or through the API:

paths:
  test:

Understood, thank you for your time!

[github-actions]

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.