增加Apache https监听，解决Nginx反向代理出现的Mixed-Content问题 #39
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
|
非常感谢PR！不过能否询问下”Nginx方向代理导致Mixed-Content问题“具体会体现在哪里呢？我自己目前用nginx直接反代Apache的http端口服务没有看到过这个报错。 |
这个bug关联 lsky-org/lsky-pro#317 ，根本原因是原项目使用后端判断协议类型，如果CDN使用HTTP回源，或者当前Docker使用Nginx反向代理http地址，会导致后端获取错误的协议，进而在构建页面时使用http协议的静态资源，导致Mixed-Content问题（https协议的网站中存在http资源）。 这种方式就是使得反向代理的协议与服务器使用的协议一致，如果服务器用了https加密，那么使用https地址进行反向代理可以让后端页面生成时使用一致的协议，避免Mixed-Content。 |
|
了解了，抱歉回复不及时，这就Merge |
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.
/etc/ssl路径中