Use a valid Content-Type when extracting token #1051
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm calling a POST request
/api/loginwith JSON payload (username, password) to get a valid JWT.When I try to parse the request I get an exception
Bad Content-Type header: cty. I cannot manually replace this header due to engine limitation (ktor), so this is the only solution to my issue.CI build OK: https://app.circleci.com/pipelines/github/DVDAndroid/filebrowser
Docker images: https://hub.docker.com/repository/docker/dvdandroid/filebrowser
Content-Type header standard: https://www.w3.org/Protocols/rfc1341/4_Content-Type.html
Sincerely I don't know why content type is
cty