Encoding header for dsn get set incorrectly#453
Merged
frankgiordano merged 1 commit intozowe:mainfrom Jan 22, 2026
Merged
Conversation
…test Signed-off-by: Kasper Helsted <helsted@vopu.dk>
730564d to
ab20c6d
Compare
frankgiordano
approved these changes
Jan 22, 2026
Collaborator
|
Thank you for this contribution! I will release this fix in an upcoming release 6.0.4. |
Collaborator
|
@KasperHelsted This is now included in the new 6.1.0 just published. Thanks. |
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
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.
While fetching data using the Zowe Java SDK, I noticed that Danish characters were rendered incorrectly.
To verify whether this was client-specific, I performed the same operation using Zowe Explorer in Visual Studio Code, where the characters appeared correctly.
I then inspected the HTTP requests sent by both clients and observed a difference in the headers. Requests from Visual Studio Code included:
X-IBM-Data-Type: text;fileEncoding=IBM-277
In contrast, requests made via the Java SDK contained:
X_IBM_TEXT: X_IBM_TEXTX_IBM_TEXT_ENCODINGOptionalLong[277]
This header format did not appear to be correct.
This PR updates the header generation to align with the structure used in the other DsnGet cases. After applying this change, I verified that Danish characters are now rendered correctly when calling Zowe through the Java SDK.