Is there a proper way to host SMP and XFTP servers behind a reverse proxy ?

未關閉
#1,744 3 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
25/100
Issue 類型
文件
描述清晰度
需要釐清
活躍度
冷清

研究方向

Start by investigating the HAProxy TCP proxy with SNI approach described in the issue, including TLS 1.3 passthrough for SMP and XFTP and sharing port 443 with other domains. Done should be a documented supported configuration or a clear explanation of the limitation and an alternative deployment approach.

由索引模型根據 Issue 內容生成。

描述

The small embedded web server for SMP is the easy piece as there is an option to use http: 8000 and so any reverse proxy can send the traffic to that.

My question is more on SMP and XFTP protocols, any of you had a chance to make it work with a HAProxy with TCP Proxy using SNI ?

My issue is that ideally it would be better to use 443 (if I only use 5223 I see this warning when launching the server: > WARNING: the clients will use port 443 by default soon.) but how can it use 443 if other domains are ?

As SMP is based on TLS1.3 is is possible to use the SSL routing based on SNI on HA Proxy ? This mode is only reading the SNI and don't touch on SSL (no offloading) and keep the TLS managed by the backends (here SMP and XFTP).

Any of you using something like this ? Or is there another alternative to host SMP/XFTP with other domains on 443 on the same IP address ? (which is a pretty common setup)

Thanks

主要語言
Haskell
星號
865
分支
125
平均合併
1 天 20 小時
30 天內合併 PR
64

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

simplex-chat/simplexmq 的其他 Issue

查看 simplex-chat/simplexmq 的全部 Issue

相似的 Issue

更多 Haskell Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。