修复client auth header 鉴权机制，经过Nginx代理之后不生效的问题 #1089
Merged
Conversation
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
Nginx代理默认会将自定义header转为纯小写, 完善client对auth header的校验逻辑，实现针对该情况的兼容
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Nginx代理默认会将自定义header转为纯小写，auth 通过后 powerjob server 返回的header为X-POWERJOB-AUTH-PASSED，经过Nginx代理之后header会自动变为 x-powerjob-auth-passed，从而导致 client 端 auth 校验失败，这种情况下会导致请求重复发送两次的问题，该修复方案实现针对此类情况的兼容。