Fix WeChat Pay profit-sharing callback signature verification line separator inconsistency #3649
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.
Problem
The
ProfitSharingServiceImpl.verifyNotifySign()
method was using platform-specific line separators (%n
) while the base implementation uses LF (\n
), causing signature verification failures in WeChat Pay Service Provider Mode profit-sharing callbacks.Root Cause
WeChat Pay signature verification requires consistent use of LF (
\n
) as line separator. The profit-sharing service was using:While the base implementation correctly uses:
The
%n
format specifier produces platform-specific line separators (LF on Unix/Linux, CRLF on Windows), causing signature verification to fail with "非法请求,头部信息验证失败" (Illegal request, header verification failed) errors.Solution
%n
to\n
to ensure consistent LF line separators across all platformsWECHATPAY/SIGNTEST/
prefix to properly handle WeChat Pay signature test trafficWxSignTestException
for signature test scenariosChanges Made
ProfitSharingServiceImpl.verifyNotifySign()
to use\n
instead of%n
WxSignTestException
This ensures consistency with other service implementations and resolves signature verification failures in profit-sharing callbacks.
Fixes #3634.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.