Fixed content type header check in aquery.#36
Open
marek-jelo-jelinek wants to merge 1 commit into
Open
Conversation
|
Verified against the live API on 2026-06-07: the endpoint now returns |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR improves the way the Content-Type header is validated for XML responses in aquery. Previously, the code depended on an exact string match (text/xml;charset=utf-8), which could fail if the header used a different case, parameter order, or the application/xml type.
The new approach is more flexible and should reliably handle any minor changes to the header on the server side.