Bonefish websocket on TLS

[petten]

On the front page of this repository/project, one reads that the daemon can be started as follows.

daemon/bonefish --realm "default" --websocket-port 9999

Does the --websocket-port cover both TLS and non-TLS uses?

How does one choose just one of them (e.g, the TLS one, and therefore forbid non-TLS use)?

Is there any other (command-line) configuration option pertaining to TLS?

[petten]

Related/an alternative:

Anyone care to share his/her experience using a proxy (such as nginx), so that bonefish can sit behind it comfortably without having to worry about TLS?

[samielhini]

I have used bonefish behind nginx. I think the only thing you have to do is add a slash to your url. I wasn't really able to make it work without the trailing slash.

[davidchappelle]

I haven't added direct support for Websocket TLS. The nginx suggestion above is a good alternative.

[petten]

Yes, I tried nginx, which worked. :-)

Also of interest is Microsoft IIS. Anyone had experience using it sort of like nginx to proxy bonefish websocket services?

The version of IIS that came with Windows 7 does not seem to work, as it does not understand the websocket protocol, thus fails to deal with the upgrade handshake when the connection is initiated.