Explicitly set content type on xhr request #649
Conversation
This file contains hidden or 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
As a user I had to introduce a proxy between the plugin and Anki actual program to work around issues with Snap packaging (Having Obsidian installed as a snap package). That proxy used to set default headers on the request and caused it to be processed incorrectly. This line prevented that for the content type header. It's important because when AnkiConnect does not recognize the content type it returns something like "AnkiConnect v.6" which cause the connection to fail.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As a user I had to introduce a proxy between the plugin and Anki actual program to work around issues with Snap packaging (Having Obsidian installed as a snap package).
That proxy used to set default headers on the request and caused it to be processed incorrectly. This line prevented that for the content type header.
It's important because when AnkiConnect does not recognize the content type it returns something like "AnkiConnect v.6" which cause the connection to fail.