We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
对于单纯想要配置静态伪装站的用户,TLS分流器内置的静态服务器己经足够。但是TLS分流器没法处理http自动重定向到https,引入额外的web服务器监听80端口的http请求可以解决。 nginx配置文件示例
server { listen 80 default_server; listen [::]:80 default_server; server_name example.com; return 301 https://example.com$request_uri; }
如此一来无论访问example.com、 http://example.com、https//example.com都可以直接显示页面,更像一个正常的网站。为什么不用nginx做为伪装站的web服务器而只用来处理80端口的转发 ?一来这样不用更动原本教程里写的TLS分流器配置文件,nginx的配置也会比较简单,但是做出来的伪装站效果一样;二来若用户有更多的web服务器需求应该有能力自行阅读分流器的文件写出他们需要的配置,也不需要看这篇教程。
example.com
http://example.com
https//example.com
The text was updated successfully, but these errors were encountered:
No branches or pull requests
对于单纯想要配置静态伪装站的用户,TLS分流器内置的静态服务器己经足够。但是TLS分流器没法处理http自动重定向到https,引入额外的web服务器监听80端口的http请求可以解决。
nginx配置文件示例
如此一来无论访问
example.com
、http://example.com
、https//example.com
都可以直接显示页面,更像一个正常的网站。为什么不用nginx做为伪装站的web服务器而只用来处理80端口的转发 ?一来这样不用更动原本教程里写的TLS分流器配置文件,nginx的配置也会比较简单,但是做出来的伪装站效果一样;二来若用户有更多的web服务器需求应该有能力自行阅读分流器的文件写出他们需要的配置,也不需要看这篇教程。The text was updated successfully, but these errors were encountered: