Never expose API-key to browser #78
Closed
Conversation
This file contains 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
using server-side configuration instead when no user input is given.
|
这样做，如果用户想要更换API-Key，就无法在网页上操作了。为了不替用户做这个选择，我提供了一个开关，用户可以自行选择是否需要隐藏该输入框。 |
|
实际上并不影响用户自行填写。提交的实现中输入框还在，用户也可以填写，只有当用户不填写时服务端才会使用默认的key，而服务端配置的key不会发送到客户端。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Never expose API-key to browser, using server-side configuration instead when no user input is given.