CenterForDigitalHumanities / CenterForDigitalHumanities/rerum_server_nodejs
Top level @id and child @id protocol
Open
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 6
- Avg merge
- 1h 25m
- Merged PRs (30d)
- 3
Description
https://store.rerum.io/v1/id/5b719a3ed5de7603cc40779f
The `@id` of this object and its internal objects are still HTTP. HTTPS applications still get Mixed Content warnings when they are parsing the object and resolving things.
When RERUM objects are asked for via HTTPS /v1/id, should we be upgrading all child item RERUM IDs to HTTPS?
Contributor guide
Assessment
This issue has not been assessed yet.