SSE Proxy Configuration (HTTPS)

Add the URL of the Content Store's change log SSE endpoint to the SSE Proxy's list of backends and set the Host header as follows:

backends:
  - uri: http://editorial.mydomain.com:8443/webservice/escenic/changelog/sse
      httpHeaders:
        Host: cue.mydomain.com

For full information about installing and configuring an SSE Proxy, see the SSE Proxy documentation.

The web server in front of the SSE Proxy must be able to handle an SSE stream without constantly disconnecting clients: It must be configured to:

Allow long-running connection
Support chunked encoding
Not buffer or cache the traffic

The following example shows a suitable nginx configuration (/etc/nginx/default-site/sse-proxy.conf) for a virtual host fronting an SSE Proxy installed on the same host as the Content Store:

location /sse {

    proxy_read_timeout     300;
    proxy_connect_timeout  300;

    proxy_pass http://editorial.mydomain.com:9080;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header Connection '';
    proxy_http_version 1.1;
    proxy_buffering off;
    proxy_cache off;
    chunked_transfer_encoding off;
  }

Once your SSE Proxy is configured, you will also need to reconfigure the change log event stream URI that the Content Store offers to clients. By default the Content Store sends clients the URI of its own SSE endpoint, but now you want clients to get their change log events from the SSE Proxy instead, so you need to set this configuration to:

sseEndpoint=https://cue.mydomain.com/sse

For detailed instructions on how to do this, see Changing the Content Engine Event Stream URI.