Just solved this, very easy - involves creating an .htaccess file in the root of your domain/subdomain file.
https://www.myintervals.com/forum/discussion/646/redirect-a-domain-to-my-intervals-domain/#Item_3
The .htaccess file approach is the only solution that will work. Only a redirect to the actual Intervals domain will work. This is because Intervals relies on the domain name to identify the account. If a CNAME is used than Intervals cannot identify the account.
As joshreeder pointed out, the redirect for .htaccess files is available in this forum post:
https://www.myintervals.com/forum/discussion/646/redirect-a-domain-to-my-intervals-domain/#Item_3
One of the hurdles in getting over this is that we want SSL to be used. Now SSL historically has been a one ip address per SSL site, therefore it wouldn't be efficient to have a different ip address per client's custom domain. Using a single domain allows intervals to use a wildcard certificate to get around this issue and use the HTTP_HOST as a hook into the project area.
However there is a way around this using SNI, here's a simplified process (there are no doubt load balancers which may complicate this process).
The process would be:
- Enable SNI in the site delivery, it appears that intervalsonline use nginx so instructions are here:
https://kbeezie.com/view/configuring-sni-with-nginx/
- Add an option on global settings to add in the custom sub domain
- A CSR would be generated for this custom subdomain to be copied by the client
- The CSR is used to purchase a certificate and then then CRT + any CA authority files uploaded into intervals
- The custom subdomain would be CNAMED to your default intervals project area i.e
custom.yourdomain.com CNAME yourclientarea.intervalsonline.com
This ensures that any ip address changes intervals would make would not affect the custom domain.
- Intervals modified to look for the custom domain and accept requests from this or from the original intervalsonline.com domain name.
If a custom domain is added I would suggest that the default intervalsonline.com domain would still continue to function, in case of a problem with the custom domain, ssl cert for example.
SNI does not have full support in all browsers, however with this being an admin system pre-requisites can be applied.
https://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI
The would be an issue with clients who continue to use ie6 which case what would happen is that these clients would get to a non domain matched page, if Intervals had a help page here for browsers that don't support SNI then this would clear up any confusion for these clients. For clients who cannot upgrade their browser they would need to use the support email address to raise a request.
All the best
Darren
1 to 10 of 10
Comments are closed.
For more Intervals help documentation, please visit help.myintervals.com