大网数据广告活动
网站运营与故障问答

Apache proxy, ws vs. wss and https

· 52CE 我爱测

O-tree is a web-based software that uses websockets. I have it working on http://server.example:81 and I want it to be in https://server.example . It almost works with <Location /> ProxyPreserveHost On RequestHeader set X-Forward…

问题原文

原帖链接 · Jori Mäntysalo · CC BY-SA 4.0

O-tree is a web-based software that uses websockets. I have it working on http://server.example:81 and I want it to be in https://server.example. It almost works with

<Location />
    ProxyPreserveHost On
    RequestHeader set X-Forwarded-Proto "https"
    ProxyPass "ws://localhost:81/"
    ProxyPass "http://localhost:81/"
</Location>

However I got an error about GET wss://server.example/create_demo_session. Hence I suppose I should somehow say "no https for ws, please". If I let out X-Forwarded-Proto-part, then the front page gives links to http://server.example instead of https://server.example.

已采纳解答

原帖链接 · Stephen Ostermiller · CC BY-SA 4.0

You can differentiate between WSS and HTTPS requests and do different proxying for them. This is the rule I used when I built a music player with a Raspberry Pi:

RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) ws://localhost:81/$1 [P,L]
RewriteRule /(.*) http://localhost:81/$1 [P,L]

The RewriteCond tests if the request is wss: and forwards those requests over ws:, other requests use the http: proxy rule.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2022-12-14)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。