With changes to web browsers (Chrome in particular) coming soon that will mark non-SSL (http://) websites as Not secure, now is the time to consider upgrading your site to SSL encryption. The first part is getting an SSL certificate and adding it to your hosting account. However, you also have to check through and adjust your site for optimal results.
This page details tips and best practices for specified accessibility standards for usage on our webpages across campus.
Please note that you should always check to make sure your content is applicable to the specified changes before incorporating changes below. Don't hesitate to ask a web developer if you have any questions about a remediation effort or an accessibility issue on a website.
To set up an external domain name with SSL encryption on an OIT Web Hosting account:
You can generate a CSR for an OIT Web Hosting site from the site's Plesk Control Panel:
To set up a website redirect from your PWP website, please follow the instructions below.
This process has been lifted from this Stackoverflow article.
Source: /(.*) Target: http://mysite.com/$1
There are dozens if not hundreds of commercial web hosting solutions available outside of Georgia Tech, but use of them for Georgia Tech related websites is not recommended for a number of reasons:
There are a number of options available to you for hosting a website at Georgia Tech, including:
SSL encryption is highly recommended for websites these days, not just because it makes user interactions with your site more secure, but also because the major browser manufacturers are starting to mark all non-SSL encrypted sites with some kind of red symbol (red padlock, red 'X' through a padlock, etc.) to better warn users not to enter sensitive information into these sites. So, from a marketing standpoint, it's going to make your site look more professional if you turn on SSL encryption, which will keep those red warning symbols from showing.
The most important security practice for web application software is to keep up with your software patches. The more commonly used the application, the greater a chance that someone out there is looking for insecure installations to hack.
For any off-campus domain (e.g. a domain that does not end in .gatech.edu), a few more steps are required for configuring the domain beyond setting the custom domain for a site in PWP.
Proper setup of the off-campus domain (and its www.{customdomain} alternative) require the following:
