phlinhng

Suggestions for improving trojan:// url format

8

For now, trojan-go use trojan-gfw compatible `trojan://` uri to pass client-side configuration. I would like to suggest that trojan-go design an extension format to support trojan-go specific features. Here is...

是Websocket不是Webservice

1

https://github.com/master-coder-ll/v2ray-web-manager/blob/master/support-https.md

I wonder if I can enable auto certification apply without port 443 occupied? I only need armor to serve plain HTTP at port 80 but I need tls cert for...

对于单纯想要配置静态伪装站的用户，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服务器需求应该有能力自行阅读分流器的文件写出他们需要的配置，也不需要看这篇教程。

#### Do you want to request a _feature_ or report a _bug_ or just a _question_? 虽然问题不大，还是提一下。 #### What's the current behavior? #### What's the expected behavior?

#### Do you want to request a _feature_ or report a _bug_ or just a _question_? 手动加入简繁转换脚本([例如这个](https://www.arao.me/website/hexo-support-jian-fan-language.html))的话，现有的页面布局必需手动调整才能新增简繁转换按钮。希望能将简繁转换整合到主题内。 #### What's the current behavior? #### What's the expected behavior?

修改 nginx 配置文件 ``` server { listen 127.0.0.1:80; server_name $your_domain; root /usr/share/nginx/html; index index.php index.html index.htm; } server { listen 0.0.0.0:80; listen [::]:80; server_name _; return 301 https://$your_domain\$request_uri; } ```

如果有人需要，可以用以下指令移除`nali-ipip` ```sh rm -rf /usr/local/bin/nali* rm -rf /usr/local/bin/ipip-nali rm -f /usr/local/share/17monipdb.datx rm -f /usr/local/share/nali.pl ```