This repository was archived by the owner on Feb 13, 2026. It is now read-only.
Write xml.Header first instead of spaces to handle XML parsers#7253
Merged
nitisht merged 1 commit intominio:masterfrom Feb 21, 2019
Merged
Write xml.Header first instead of spaces to handle XML parsers#7253nitisht merged 1 commit intominio:masterfrom
nitisht merged 1 commit intominio:masterfrom
Conversation
5884d0f to
b074eb0
Compare
Codecov Report
@@ Coverage Diff @@
## master #7253 +/- ##
==========================================
- Coverage 48.49% 48.45% -0.04%
==========================================
Files 295 294 -1
Lines 45888 45900 +12
==========================================
- Hits 22252 22242 -10
- Misses 21605 21622 +17
- Partials 2031 2036 +5
Continue to review full report at Codecov.
|
b074eb0 to
8740a64
Compare
8740a64 to
fb4f76b
Compare
33e3023 to
5fe2894
Compare
Contributor
|
with this diff i got: |
Member
Author
|
ah, crap there are double XML headers @krishnasrinivas - it should be added outside not here... |
33e0155 to
6c2a052
Compare
Member
Author
|
Fixe @krishnasrinivas @Praveenrajmani PTAL - the functionality of the fix is different now. |
23178c1 to
3f584c0
Compare
Member
Author
|
Fixed @krishnasrinivas @Praveenrajmani - PTAL |
3f584c0 to
5752c85
Compare
Clients like AWS SDK Java and AWS cli XML parsers are unable to handle on `\r\n` characters to avoid these errors send XML header first and write white space characters instead. Also handle cases to avoid double WriteHeader calls
5752c85 to
f7ced1a
Compare
Mint Automation
7253-f7ced1a/mint-xl.sh.log: |
krishnasrinivas
approved these changes
Feb 21, 2019
Praveenrajmani
approved these changes
Feb 21, 2019
9 tasks
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Write xml.Header first instead of spaces to handle XML parsers
Motivation and Context
Clients like AWS SDK Java and AWS cli XML parsers are
unable to handle on
\r\ncharacters to avoid theseerrors send XML header first and write white space characters
instead.
Also handle cases to avoid double WriteHeader calls
Regression
In a way yes
How Has This Been Tested?
Using AWS SDK Java upload manager and AWS CLI upload
Types of changes
Checklist:
mintPR # here: )