Skip to Main Content
HCL Domino Ideas Portal

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

Status No Plans to Implement
Workspace Domino
Categories Security
Created by Guest
Created on Jul 8, 2021

Option to force Https while using @urlopen code with computed Url and relative path.

There are requirements when domino server is behind the SSL offloader and domino serer is not SSL enabled. If there are @urlopen code used with computed Url and relative path. Domino is adding by default http with the server FQDN , So this code is not working from browser with https ( with SSL offloader in place).


Please find the sample code below:

urlComputed:="/app/Test.nsf?OpenForm";

@URLOpen(urlComputed)


There is option to add full path of the server with https:// in the code to make it work, but there may be relative path used in many places in the code which is not possible to replace.

Or use http response header rule as described in the below KB article.

https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0039406

But it will replace the incoming url with specific FQDN. It will not just replace the http to https . If the requirement is for multiple FQDN then this workaround is not feasible.


So raising this enhancement request to check the possibility to add the option to force https from Domino end if Domino server is accessed from behind the SSL offloader.

  • Attach files
  • Admin
    Thomas Hampel
    Reply
    |
    Jan 6, 2023

    Even for servers that are behind an SSL offloader, you should use HTTPS between the proxy and your Domino server backend.

    So there are no plans to provide this feature because the recommended approach is to enable HTTPS for Domino in all cases - this will make the environment more secure.