Avoid loading insecure content (e.g. external CSS,JS libraries) when using secure webpages.

12606
Reporter: jcuadra
Type: Improvement
Summary: Avoid loading insecure content (e.g. external CSS,JS libraries) when using secure webpages.
Priority: Minor
Resolution: WontFix
Status: Closed
Created: 2013-01-18 17:00:14.751
Updated: 2013-08-29 14:45:59.18
Resolved: 2013-02-26 18:29:42.809
        
Description: If applicable anywhere on our portal (or CAS pages), avoid loading insecure content through secure webpages. The recommendation is to use protocol-less URLs so the "browser works out which protocol it should be using based on the page that loaded it (http://blog.benpowell.co.uk/2011/08/https-and-http-protocol-less-or.html)

*RFC3986 s4.2*
http://tools.ietf.org/html/rfc3986#section-4.2]]>
    

Author: trobertson@gbif.org
Comment: Since we don't use HTTPS anymore (no CAS) this has become redundant.  Closing for that reason alone, expecting HTTPS introduction to cover this should it ever be needed.
Created: 2013-02-26 18:29:42.833
Updated: 2013-02-26 18:29:42.833