在openshift中运行时python websocket失败

Question

下面是我在虚拟机中使用的缩短代码。

from autobahn.twisted.websocket import WebSocketServerProtocol, WebSocketServerFactory, listenWS
from autobahn.twisted.resource import WebSocketResource

class MyServerProtocol(WebSocketServerProtocol):
    def onConnect(self, request):
        stuff...
    def onOpen(self):
        stuff...
    def onMessage(self,payload):
        stuff...


factory = WebSocketServerFactory(u"ws://0.0.0.0:8080")
factory.protocol = MyServerProtocol
resource = WebSocketResource(factory)

root = File(".")
root.putChild(b"ws", resource)
site = Site(root)

reactor.listenTCP(8080, site)
reactor.run()

客户端的连接部分如下：

var wsuri;
var hostname = window.document.location.hostname;
wsuri = "ws://" + hostname + ":8080/ws";

if ("WebSocket" in window) {
    sock = new WebSocket(wsuri);
} else if ("MozWebSocket" in window) {
    sock = new MozWebSocket(wsuri);
} else {
    log("Browser does not support WebSocket!");
    window.location = "http://autobahn.ws/unsupportedbrowser";
}

openshift配置如下：

Firefox can’t establish a connection to the server at ws://openshiftprovidedurl.net:8080/ws.

wscat -c ws://openshiftprovidedurl.net/ws

error: Error: unexpected server response (400)

openshift中的应用程序日志显示如下：

2018-04-03 01:14:24+0000 [-] failing WebSocket opening handshake ('missing port in HTTP Host header 'openshiftprovidedurl.net' and server runs on non-standard port 8080 (wss = False)')
2018-04-03 01:14:24+0000 [-] dropping connection to peer tcp4:173.21.2.1:38940 with abort=False: missing port in HTTP Host header 'openshiftprovidedurl.net' and server runs on non-standard port 8080 (wss = False)
2018-04-03 01:14:24+0000 [-] WebSocket connection closed: connection was closed uncleanly (missing port in HTTP Host header 'openshiftprovidedurl.net' and server runs on non-standard port 8080 (wss = False))

如有任何协助，我们将不胜感激！

Answer 1

Graham Dumpleton一针见血地说，我修改了代码

factory = WebSocketServerFactory(u"ws://0.0.0.0:8080")

至

factory = WebSocketServerFactory(u"ws://0.0.0.0:8080", externalPort=80)

它纠正了这个问题。我不得不修改我的索引以指向正确的websocket，但我现在能够连接了。