Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Add basic reverse-proxy functionality to the Nomad websocket proxy server (nwsp)
Adding Nomad to a Domino server (incl. the native 'Nomad websocket server') 'steals' the port 443 from Domino if one wants Nomad to be available on standard https://. Also Nomad default listens on port 9443, users expect it at 443.
If the Domino server hosts other web-apps as well, a reverse-proxy like nginx or Safelinx is needed to dispatch web-traffic between Nomad and Domino. This requires additional services and with its own certificate handling.
I propose to give the Nomad server some basic reverse-proxy functionality to forward all-other / specific-urls to a Domino webserver (on another port).