- From: Sarven Capadisli via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Nov 2015 14:25:52 +0000
- To: public-annotation@w3.org
+1 to serving secure `http` - as opposed to `https` - resources (since TLS is on a lower level any way). The catch is that, existing tooling/UI gives special treatment to `https`. On the other hand, serving secure `http` may quietly workaround (for better or worse) mixed content, .., sticking to singular vocabulary IRIs (as opposed to redirecting or mapping between `http` and `https`). -- GitHub Notif of comment by csarven See https://github.com/w3c/web-annotation/issues/103#issuecomment-154421383
Received on Friday, 6 November 2015 14:25:53 UTC