Consider Mechanism to upgrade insecure requests about solid-spec

[deiu]

I wonder if this is a real issue for us. Mixed content problems appear when you have an application that runs on HTTPS and you're trying to fetch resources over HTTP. The Web is moving to HTTPS, and Solid is no exception. Both ldnode and gold run first and foremost over HTTPS, which means that clients won't risk getting mixed content warnings when fetching resources from them. I think it's the rest of the Web that rather needs to implement the upgrade mechanism.

[csarven]

This is particularly about error prevention, and how Solid can foster a friendly UX. It is not directly a Solid platform issue b/c it has to do with the data - which may exist and retrieved from anywhere. Hence, I labelled the original issue as a feature. I think the core concern is that, for the foreseeable future, it is likely that applications which run on https uses data with http references.

[deiu]

Yes, but there is nothing we can do on our side. It's about moving to HTTPS.

[deiu]

Closing this issue since it doesn't involve an action on our part.