influxdata / influxdata/influxdb
/authorizations/{authID} PATCH - missing or invalid request body results in HTTP 500
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
Testing against the API
1. prepare a PATCH request to be sent to the endpoint `/authorizations/{authID}`
2. do one of the following
1. leave out the request body
2. Use non string values for either the `status` or the `description` properties. e.g. `{ foo: "bar"}` or `Math.PI`
3. send the request
__Expected behavior:__
Expected a missing or invalid request body to be caught by the server and that an HTTP 400 status would be returned with a message that the request body is missing or that properties are invalid.
__Actual behavior:__
The server returned HTTP 500
__Environment info:__
Testing against K8S-IDPE
latest commit
```
commit 0e28da062cc917e43809c80f235976d244947bb0 (HEAD -> master, origin/master, origin/HEAD)
Author: influx-acs[bot] <107396960+influx-acs[bot]@users.noreply.github.com>
Date: Tue Dec 27 20:12:20 2022 +0000
```
Contributor guide
Research direction
Start by reproducing the PATCH request against /authorizations/{authID} with no body and with non-string status or description values. Trace the request validation and error handling for this endpoint. Done means malformed or missing bodies return HTTP 400 with a message identifying the invalid request.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100