Last modified: 2014-11-01 22:14:20 UTC
All URIs we generate should use the "https://" schema prefix. There are two main cases: * Well-known URIs used in the data, e.g. for Calendars and Globes. These can easily be changed in the software, but all places where URIs in data get compared to constants need to be identified and modified to apply the required normalization before comparing. * URIs we expose for the wiki's entities (as well as data types, etc). We should automatically use https URIs here only of the present site actually supports HTTPS. But if it does, we should expose https URIs even if the current request was handled via unencrypted http.
(In reply to comment #0) > All URIs we generate should use the "https://" schema prefix. There are two > main cases: > > * Well-known URIs used in the data, e.g. for Calendars and Globes. These can > easily be changed in the software, but all places where URIs in data get > compared to constants need to be identified and modified to apply the > required > normalization before comparing. > > * URIs we expose for the wiki's entities (as well as data types, etc). We > should automatically use https URIs here only of the present site actually > supports HTTPS. But if it does, we should expose https URIs even if the > current > request was handled via unencrypted http. Couldn't we use protocol-relative URLs instead?
I'm pretty sure this has long been fixed.
