[FOLIO-291] HTTPS access to developer website Created: 01/Sep/16  Updated: 12/Nov/18  Resolved: 09/Feb/18

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Nassib Nassar Assignee: Peter Murray
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 15 minutes
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-832 Build and deploy dev website via CI Closed
Sprint:

 Comments   
Comment by John Malconian [ 01/Sep/16 ]

GitHub Pages does not support HTTPS for custom domains.

There are two potential solutions if we need to support HTTPS. Number one is to use a 3rd party like CloudFlare to proxy HTTPS to the GitHub Site. This involves more DNS changes on EBSCO’s end and a configuration at CloudFlare (SSL Certs, etc). To be clear, this would result in HTTPS from the client to CloudFlare only. Connections from CloudFlare to GitHub would still be HTTP. I doubt that this would be a big deal given that HTTPS in this particular instance is more of a marketing thing and not an actual security issue…The second solution would be just to host the website on a different system (not GitHub).

Comment by John Malconian [ 01/Sep/16 ]

It should be clarified that using a CloudFlare reverse proxy means that the domain (or subdomain in this case) needs to use CloudFlare's NS servers. folio.org and dev.folio.org domains are managed by EBSCO and hosted by GoDaddy. They would either need to make 'dev.folio.org' a subdomain of folio.org and create NS records for the subdomain that point to CloudFlare's NS servers OR configure CloudFlare's nameservers for the entire folio.org domain. Either way, since EBSCO manages the domain name, this is something they would want/need to manage instead of Index Data.

Comment by John Malconian [ 01/Sep/16 ]

The other option, of course, is to host the Dev site on a different server i.e not GitHub.

Comment by John Malconian [ 08/Sep/16 ]

Re-assigning back to Jakub.

Comment by Peter Murray [ 09/Feb/18 ]

Now done with the move to AWS CloudFront.

Generated at Thu Feb 08 23:04:41 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.