Skip to content

fix(http): avoid parsing XML response bodies as YAML #3986

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 5 commits into from
Jun 27, 2025
Merged

fix(http): avoid parsing XML response bodies as YAML #3986

merged 5 commits into from
Jun 27, 2025

Conversation

lukaszzazulak
Copy link
Contributor

Closes #3844

char0n
char0n reviewed Jun 26, 2025
View reviewed changes
char0n
char0n reviewed Jun 26, 2025
View reviewed changes
char0n
char0n suggested changes Jun 26, 2025
View reviewed changes
Copy link
Contributor

@char0n char0n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nicely done! Please have a look at my CRCs if you find them valid

@lukaszzazulak lukaszzazulak mentioned this pull request Jun 27, 2025
Closed
@lukaszzazulak lukaszzazulak merged commit b205dc3 into master Jun 27, 2025
8 checks passed
@lukaszzazulak lukaszzazulak deleted the fix(http)-avoid-parsing-XML-response-bodies-as-YAML branch June 27, 2025 09:04
swagger-bot pushed a commit that referenced this pull request Jun 27, 2025
@semantic-release-bot
chore(release): cut the 3.35.6 release [skip ci]
4ca3e3c 
## [3.35.6](v3.35.5...v3.35.6) (2025-06-27)

### Bug Fixes

* **http:** avoid parsing XML response bodies as YAML ([#3986](#3986)) ([b205dc3](b205dc3)), closes [#3844](#3844)
@swagger-bot
Copy link
Contributor

🎉 This PR is included in version 3.35.6 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@glowcloud glowcloud Awaiting requested review from glowcloud

1 more reviewer

@char0n char0n char0n approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

XML response will be parsed wrong by yaml parser if it has semicolon
3 participants
@lukaszzazulak @swagger-bot @char0n