Fix LT HTTP request Content-Type #276
Open
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
The LanguageTool check endpoint actually expects an HTTP request with an "application/x-www-form-urlencoded" Content-Type. Currently ltex-ls uses the "application/json" Content-Type for the HTTP request, but this does not play well with some third-party tools that follow the same LanguageTool API like https://github.com/cpg314/ltapiserv-rs. The official LanguageTool HTTP server does not seem to be affected by this bug. See the API documentation: https://languagetool.org/http-api/swagger-ui/#!/default/post_check
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.
The LanguageTool check endpoint actually expects an HTTP request with an "application/x-www-form-urlencoded" Content-Type. Currently ltex-ls uses the "application/json" Content-Type for the HTTP request, but this does not play well with some third-party tools that follow the same LanguageTool API like https://github.com/cpg314/ltapiserv-rs.
The official LanguageTool HTTP server does not seem to be affected by this bug.
See the API documentation: https://languagetool.org/http-api/swagger-ui/#!/default/post_check