We have a legacy sub-domain (e.g. mail.old.com) that needs to redirect to mail.new.com. Same server, same assets... mail.new.com works and is configured with SSL (Internet Site doc). mail.old.com does not have a site document, nor is there an SSL configuration. In short, users should be able to enter mail.old.com and be redirected to mail.new.com (so no SSL certificate errors are encountered). Been a long time, but am certain I've done. Thanks in advance, team.
This is for internal (LAN clients) and not external ones. We're handling successfully with rules via external service. Allowing Domino to handle redirect seemed like an obvious option.
Have you tried the Web Site Rule Redirection?
Creating a Web Site Rule document
https://help.hcl-software.com/domino/14.0.0/admin/conf_creatingawebsiteruledocument_t.html
Hello Jessie, thanks for your response. I have tried Redirection (and Substitution...) but noticed that the hover help states to not use hostname or start with protocol on "Incoming URL..." I need anything with mail.old.com to be replaced with mail.new.com. For example, https://mail.old.com -> https://mail.new.com or mail.old.com/test.nsf -> mail.new.com/test.nsf (same server, same assets). I want the server to replace/redirect before the SSL. If it has to resolve https://mail.old.com then browsers will get certificate error because there is no configured site document with KYR file.
Hello.
The Domino server has a website rules document, which allows you to redirect to a different site with a specified URL pattern.
However, URL patterns in website rule document cannot contain "protocols" or "hostnames" and therefore cannot be used for your requirement.
There is one solution for this. Please see this article.
https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0024648
Along with this setting, use the following settings.
[Server document] - [Ports] - [Internet Ports] - [TCP/IP port status]: "Redirect to TLS"
We believe we can achieve your functionality with these settings.
You are already using a different solution, but we encourage you to try it.
Regards,
Shigemitsu Tanaka
Thanks, Shigemitsu, just posted a response to Jessie re: no protocols/hostnames. I'm checking out your links now.
Update: I read the article and it's interesting. I'm a bit confused because the source site document (and corresponding site rule) is IP address-based. How would it know to replace/redirect mail.old.com if only the IP address is listed?
Hi Michael.
The website rules document is tied to the website document.
Specify the old hostname in ‘Host names or address mapped to this site:' of the website document.
Regards,
Shigemitsu Tanaka
Thanks, appreciate the quick response. I am attempting now. I don't need to configure SSL in the mail.old.com site document above, right? The target site document (mail.new.com) exists and is configured (SSL).
Update: Thanks, Shigemitsu, it worked! I'm getting some sporadic issues but think it's cache-related.