Avoid mixed-content error with JSON-LD context in HTTPS

[csarven]

Please Indicate One:

• Editorial
• Question
• Feedback
• Blocking Issue
• Non-Blocking Issue

Please Describe the Issue:

If a document is loaded over HTTPS, JSON-LD libraries are subject to getting the mixed-content error in the browser if @context uses HTTP: https://www.w3.org/ns/activitystreams

Perhaps change (especially the examples) to use https://www.w3.org/ns/activitystreams to avoid this possibility altogether.

[csarven]

There is an equivalent issue at w3c/web-annotation#347

[evanp]

I'm going to mark this at-risk that we may also support HTTP

[evanp]

I've added in a note about whether we would use http-only. I'm not sure of what the use-case is. @jasnell any ideas? can we just drop http: and use https: for everything?

[jasnell]

https for everything is fine but... that would affect the @context URLs. It would mean that all context URLs would need to use https: or risk running into the same kind of mixed-content error.

[csarven]

See also w3c/web-annotation#347 (comment)

[evanp]

All the examples use the HTTPS URL now; it also resolves correctly. So I think this can be safely closed.