|
|
|
@ -545,7 +545,19 @@ In some scenarios, the server can send incomplete or corrupted frames. This can |
|
|
|
|
|
|
|
|
|
|
|
### HTTP API |
|
|
|
### HTTP API |
|
|
|
|
|
|
|
|
|
|
|
TODO |
|
|
|
The server can be queried and controlled with an HTTP API, that must be enabled by setting the `api` parameter in the configuration: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
```yml |
|
|
|
|
|
|
|
api: yes |
|
|
|
|
|
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The API listens on `apiAddress`, that by default is `127.0.0.1:9997`; for instance, to obtain a list of active paths, run: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
``` |
|
|
|
|
|
|
|
curl http//127.0.0.1:9997/list |
|
|
|
|
|
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Full documentation of the API is available on the [dedicated site](https://aler9.github.io/rtsp-simple-server/). |
|
|
|
|
|
|
|
|
|
|
|
### Command-line usage |
|
|
|
### Command-line usage |
|
|
|
|
|
|
|
|
|
|
|
|