Griffith’s website now available on HTTPS


Secure HTTPSGriffith’s public website (griffith.edu.au) and other sites hosted on the Squiz Matrix content management system (CMS) were updated on 15 July 2015 to exclusively use HTTPS to secure communications with the web server.

Apart from securing our web pages in transferring data, this change raises the quality and reputation of our web presence. According to Google, this will gradually enhance search results for our site (HTTPS as a ranking signal (2014) Google Webmaster Central Blog).

Over the three-month project, the Project Team completed detailed planning and testing that allowed for a lot of small but important changes to be applied prior to 15 July.

Along the way the Project Team discovered and addressed a range of other issues, not directly caused by changing to HTTPS, but which have delivered benefits in page performance, content quality and general user experience. These benefits will continue beyond the project.

Although there were some minor unpredicted issues requiring specific investigation and fixes on the day – to be expected given the complexity and potential impacts of the changes – the migration went well and there are very few outstanding concerns.

Also, as expected, there were some other issues reported on the day that were unrelated and pre-existing and were only discovered because of the focus on actively testing sites and pages within the site.

The change has provided a marginal improvement in the performance of the page load and file retrieval speeds for griffith.edu.au. The Project Team says this benefit was achieved through the overall review and tidying of the network settings as well as further tuning of the CMS server.

Many thanks go to the Project Team and other support staff for all their efforts and focus on an excellent project outcome. This includes: Andrew Williams, Leanne Towerzey, Giscard Brehon, Nathan Judson, Kane Tapping, Colin Morris, Carlton Davison, Jeff Braine and Chris Gay.

Thanks also to the general web publishing community and the publishers who tested their sites before the migration and subsequently reported issues and, where necessary, made changes to their sites to accommodate the use of HTTPS.

More information about the project is available from the HTTPS Project website.

More information on HTTPS can be found on Wikipedia.



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s