search

indieweb / microsub

For tracking issues on the Microsub specification
24 stars 1 forks source link

Non https content #19

Open grantcodes opened 6 years ago

grantcodes commented 6 years ago

It's quite normal for people not to have their site on https, this causes issues with readers having mixed content issues.

Should the server be able to proxy images and content via https or not?

aaronpk commented 6 years ago

That would be an interesting feature that the microsub server could provide to clients. It does seem like this will always be a problem.

grantcodes commented 6 years ago

The main cause is almost certainly going to be images so it is tangentially related to #2 as well

aaronpk commented 6 years ago

As of a few days ago, Aperture now downloads any media resources it encounters and rewrites the URLs in the post to its own copy it is hosting. You shouldn't need to do anything differently in the client, and all the URLs will be https now.

I'm not sure this needs to be something in the spec, since the Microsub server can just rewrite the URLs transparently if it wants.

jalcine commented 5 years ago

This does sound a bit of out of scope of the spec but could probably go in a “How to Solve for X” situation. Only concern would be highlighting in Microsub clients that need the canonical post versus using exactly what the Microsub server provided.

(Originally published at: https://v2.jacky.wtf/post/39df669b-43eb-4d8b-b546-10d978af9e19)