A colleague of mine is in the process of exchanging out our Apache ws
proxy with an HAProxy configuration, but we seem to be running into 400
"400 Bad Request": which one is generating these responses? HAProxy or Autobahn?
If Autobahn, try removing the "url" parameter from where you create your WebSocketServerFactory:
factory = WebSocketServerFactory("ws://example.com:9000")
factory = WebSocketServerFactory()
If the URL is provided, this (and the externalPort) parameter will lead to some checking Autobahn does: the HTTP/GET request host header matches the host/port the server (Autobahn) runs on. With a reverse proxy in front, that'll be no longer be as simple, since the proxy usually listens on different port than Autobahn, but the request still contains the external port. If you remove URL parameter, Autobahn will simply skip those checks.
errors. Our environment is within the EC2 cloud and we are attempting to
access port 443 for HAProxy (which is where SSL is terminated), then
allows the connection to proceed to an underlying server running
Autobahn on port 9000. Note that SSL is not enabled at all on the
That's fine: you want the proxy to terminate the SSL, and balance accross backend nodes .. that's how it works normally.
Am 09.06.2014 19:34, schrieb Patrick Santora:
Here is our current configuration:
bind *:443 ssl crt /etc/ssl/certs/ws.proxy.dev.pem
# acl is_websocket path_beg -i /ws/
acl is_websocket hdr(Upgrade) -i WebSocket
acl is_websocket hdr_beg(Host) -i ws
acl is_websocket hdr_beg(Host) -i wss
use_backend www_ws if is_websocket
timeout queue 5000
timeout server 5000
timeout connect 5000
timeout tunnel 86400000
server serverA 220.127.116.11:9000
For more information about the current setup please refer to this
You received this message because you are subscribed to the Google
Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to autobahnws+...@googlegroups.com
For more options, visit https://groups.google.com/d/optout.