Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
HTTPS support #173
In order to work with HTTPS, modules must not hardcode
Modules using o-assets are working well already, but demos and docs still have some http:// URLs, e.g.
is quite common.
Just in case I suggest adding requirement to the Origami spec that JS, CSS and resources in CSS are always linked to using protocol-relative URLs.
The only downside is that
Not really concerned about demos and docs, though for best practice I agree they should really use protocol relative URLs (within wide tolerances, I'm not concerned about performance of older browsers, only compatibility).
I'll clarify in the spec that modules must not embed references to protocol specific URLs.