[
https://issues.apache.org/jira/browse/GEODE-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209159#comment-17209159
]
ASF subversion and git services commented on GEODE-8569:
--------------------------------------------------------
Commit 496541a5ebd9c50b7abf61d38ea91c981a37f1c3 in geode-native's branch
refs/heads/develop from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=496541a ]
GEODE-8569: Add missing method to ClientMessageDecoder (#663)
- This would be called, and thus throw an exception, for client logs using
AuthInitialize
- Also added v10.0.3 to version lookup for regex function dispatcher.
Apparently we'd
never tried to decode a v10.0.3 log before, go figure
- geode-native only dumps up to 8KB of a message, then truncates, so
just catch all exceptions reading a message and add an error message to
the JSON output for that message
Co-authored-by: Blake Bender <bbl...@vmware.com>
> Missing message security footer check in gnmsg
> ----------------------------------------------
>
> Key: GEODE-8569
> URL: https://issues.apache.org/jira/browse/GEODE-8569
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Blake Bender
> Assignee: Blake Bender
> Priority: Major
> Labels: pull-request-available
>
> In an older version of the `gnmsg.py` script, there was a function called
> request_requires_security_footer that returned a boolean based on the message
> name, indictating whether or not the message needed the security footer in a
> server conversation with authentication. In the refactor that moved the
> client message decoding into a class, this method was left out, so attempting
> to decode messages from a client log that used AuthInitialize will throw an
> exception attempting to call this missing function. We need to add this call
> to the ClientMessageDecoder class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
