Zaqar: Bind to IP, not proxied host

Zaqar's websocket endpoint is binding to the proxied hostname instead of
the actual IP that the service should be listening on. This is not
correct as that interface is used by HAProxy.

Change-Id: I3e528ef072a8d21984e4d4b05b41de99be5b1d0d
Closes-Bug: #1751779
This commit is contained in:
Juan Antonio Osorio Robles 2018-02-26 16:21:13 +02:00
parent 6894552a0d
commit 3ba9190749
1 changed files with 2 additions and 2 deletions

View File

@ -112,8 +112,8 @@ outputs:
- {get_param: Debug }
- {get_param: ZaqarDebug }
zaqar::server::service_name: 'httpd'
zaqar::transport::websocket::bind: {get_param: [EndpointMap, ZaqarInternal, host]}
zaqar::transport::websocket::notification_bind: {get_param: [EndpointMap, ZaqarInternal, host]}
zaqar::transport::websocket::bind: {get_param: [ServiceNetMap, ZaqarApiNetwork]}
zaqar::transport::websocket::notification_bind: {get_param: [ServiceNetMap, ZaqarApiNetwork]}
zaqar::wsgi::apache::ssl: {get_param: EnableInternalTLS}
zaqar::wsgi::apache::bind_host: {get_param: [ServiceNetMap, ZaqarApiNetwork]}
zaqar::message_pipeline: 'zaqar.notification.notifier'