feat: add GBK charset decoding support for callback notifications#248
Open
tc6-01 wants to merge 1 commit into
Open
feat: add GBK charset decoding support for callback notifications#248tc6-01 wants to merge 1 commit into
tc6-01 wants to merge 1 commit into
Conversation
Add GetTradeNotificationWithCharset and DecodeNotificationWithCharset methods to automatically decode GBK-encoded fields (Subject, Body, BuyerLogonId, PassbackParams, RefundReason) to UTF-8 after signature verification. The charset is extracted from the Content-Type header to determine if GBK decoding is needed.
Author
|
@smartwalle hi 大佬，有一个回调时的隐藏 bug，这个看看能不能集成下 |
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
1 participant
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.
Add GetTradeNotificationWithCharset and DecodeNotificationWithCharset methods to automatically decode GBK-encoded fields (Subject, Body, BuyerLogonId, PassbackParams, RefundReason) to UTF-8 after signature verification.
The charset is extracted from the Content-Type header to determine if GBK decoding is needed.
Here are some talk with alipay
