Bram's Dev Blog

home

100 Days of Code Day 73 - Analyzer HTTPs

05 Nov 2018

Input field for analyzing an item

In the current repository detail screen, a user can add a url to an item. However, it’s enforced that this url starts exactly with the repository URL. Because I want to support both http and https variants, I want to make this check softer to only check for the hostname.

Remove URL Prefix from String (http:/, www, etc.) led me to the use of java.net.URI for comparing the hostnames.

Locally, it seems to work great now. On the server however, the items are not successfully detected on Google Scholar. In order to see what’s up, I added additional logging. If that doesn’t work out, I can also look into attaching a remote debugger to figure it out.

Day 73 Plan

Investigate on the server with my additional logging to detect the root cause for difference in behaviour locally vs on the server.

Ask my colleagues for assistance to access the assets and hopefully get a successful test run in place for the language switch.

Future days - DSpace 7 Angular

Future days - Analyzer.atmire.com work

Future Days - Productivity

Future days - Jekyll http://bram-atmire.github.io/ site

Future Days - Atmire.com work

Investigate and work on search engine optimization (SEO) for the main atmire.com website.

Future Days - Learning just for learning

Sustainability challenge - Finish before Christmas

If I continue like October, I could hit day 68 by end of October and day 98 by end of November.