os400: getpeername() and getsockname() return ebcdic AF_UNIX sockaddr, #4214
Conversation
@monnerat this doesn't seem to get any other OS/400 users to review. The question is then mostly if you think we should land this anyway since it is the right way and probably right, or if we should just not do it and wait for the problem to hurt some users who can work on a fix then? |
@bagder: What I am sure is the values returned by these 2 system functions will appear to curl as garbage when applied to unix sockets ! the commit is supposed to fix that. |
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.
As libcurl now uses these 2 system functions, wrappers are needed on os400
to convert returned AF_UNIX sockaddrs to ascii.
This is a follow-up to commit 7fb54ef.
See also #4037.
I would appreciate a compilation test prior to commit, maybe by @jonrumsey. Thanks in advance.