Bug: Management endpoints require Content-Type header even if no request body needed #1040
Assignees
Labels
bug
Something isn't working
community requested
Issues requested by our community
released
Released, waiting for feedback
Comments
nagyesta
moved this from Todo for next increment
to In progress
in Lowkey Vault Roadmap
nagyesta
added a commit
that referenced
this issue
Jun 28, 2024
…est body needed - Removes Content-Type header requirement from GET and DELETE endpoints - Updates tests Updates #1040 {patch} Signed-off-by: Esta Nagy <[email protected]>
nagyesta
added a commit
that referenced
this issue
Jun 28, 2024
…est body needed - Removes Content-Type header requirement from GET and DELETE endpoints - Updates tests Updates #1040 {patch} Signed-off-by: Esta Nagy <[email protected]>
5 tasks
nagyesta
added a commit
that referenced
this issue
Jun 28, 2024
…est body needed (#1042) - Removes Content-Type header requirement from GET and DELETE endpoints - Updates tests Updates #1040 {patch} Signed-off-by: Esta Nagy <[email protected]>
|
Hi @JoeS-Bosch, |
|
Hi, |
github-project-automation
bot
moved this from In progress
to Released
in Lowkey Vault Roadmap
|
Hi, |
|
Hi, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
All your endpoint require Content-Type to be set to 'application/json'. While swagger does this implicitely, you have to create a workaround for programmatic HttpClients (e.g. in C#, I have to add an empty StringContent to the body).
Normally, get and delete requests, don't need a body or this type of header.
To reproduce
Steps to reproduce the behavior:
Expected behavior
Content-Type headers are not necessary when there is no required request body
Actual behavior
Content-Type headers are enforced to be set
The command you used
N/A
A minimal project that can be used to reproduce the issue
N/A
Environment
Additional context
Reported by @JoeS-Bosch
The text was updated successfully, but these errors were encountered: