feat: communicate outdated app/api client version

This commit is contained in:
Rainer Killinger
2023-08-25 16:01:51 +02:00
committed by Thea Schöbl
parent e0b7e616b3
commit cb196afded
2 changed files with 9 additions and 7 deletions

View File

@@ -31,10 +31,11 @@ To Provide your own configuration file you can create a `default.json` file in t
## Status Codes
- OutdatedVersions return a `HTTP 404`
- ActiveVersions return a `HTTP 503` if currently unavailable or the given code by running backend-node
- Unsupported versions (not configured as outdated or active) return a `HTTP 404`
- Successfull reponses come with a `HTTP 200`
- No version header given returns a `HTTP 300`
- ActiveVersions return a `HTTP 503` if currently unavailable or the given code by running backend-node
- OutdatedVersions return a `HTTP 426`
- Unsupported versions (not configured as outdated or active) return a `HTTP 426`
**NOTE:** The default configuration expects the client to set a version header: `X-StApps-Version=<version of app>`