Update tokenAuth.go 在处理敏感数据时,请仔细评估并确保适当的安全性 #563
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.
通过将用户名或其他标识信息放置在响应头部分,可能调试和故障排除过程中可能会有帮助,可以快速识别请求所属的用户。
但是:
通常情况下,不建议将敏感的用户信息直接暴露在响应头中,因为响应头可以被轻易地查看和获取。
由于 HTTP 响应头字段是公开的,因此请确保不要在这些字段中包含敏感信息。如果用户信息包含敏感数据,最好将其存储在响应体中
在处理敏感数据时,请仔细评估并确保适当的安全性
A similar PR may already be submitted!
Please search among the Pull request before creating one.
Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
For more information, see the
CONTRIBUTING
guide.Summary
This PR fixes/implements the following bugs/features
Explain the motivation for making this change. What existing problem does the pull request solve?
Test plan (required)
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
Code formatting
Closing issues
Fixes #