[jboss-jira] [JBoss JIRA] (DROOLS-1321) Prefer https over http for absolute links on drools.org, optaplanner.org, jbpm.org and kiegroup.org

[Geoffrey De Smet (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey De Smet updated DROOLS-1321:
-------------------------------------
    Description: 
Motivation:
1) Chrome has "a long-term plan to mark all HTTP sites as non-secure."
https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html
2) SEO: Google/Bing penalize website (lower ranking) that use http or mix http and https.

To do:
- Change all absolute links on our websites _and in our user manuals_ that lead to redhat.com, jboss.org, drools.org, optaplanner.org, jbpm.org and kiegroup.org to https.
- This includes canonical meta elements
- This includes tabzilla.js/.css loading of images (those actually give us the mixed https and http errors in chrome's inspect tooling if you go to https://www.drools.org today)
- This does not include external links, such as to wikipedia etc.

Keep an eye out on google webmaster tools to verify this doesn't introduce broken links.

Exceptions:
- ci.optaplanner.org must be on http, because those sites don't work over https...

Note: I've asked eng-ops to do ssl monitoring of our websites. So basically no risk of out of date certifications etc.

  was:
Motivation:
1) Chrome has "a long-term plan to mark all HTTP sites as non-secure."
https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html
2) SEO: Google/Bing penalize website (lower ranking) that use http or mix http and https.

To do:
- Change all absolute links on our websites _and in our user manuals_ that lead to redhat.com, jboss.org, drools.org, optaplanner.org, jbpm.org and kiegroup.org to https.
- This includes canonical meta elements
- This includes tabzilla.js/.css loading of images (those actually give us the mixed https and http errors in chrome's inspect tooling if you go to https://www.drools.org today)
- This does not include external links, such as to wikipedia etc.

Keep an eye out on google webmaster tools to verify this doesn't introduce broken links.

Exceptions:
- ci.optaplanner.org must be on http, because those sites don't work over https...



> Prefer https over http for absolute links on drools.org, optaplanner.org, jbpm.org and kiegroup.org
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DROOLS-1321
>                 URL: https://issues.jboss.org/browse/DROOLS-1321
>             Project: Drools
>          Issue Type: Task
>          Components: build
>            Reporter: Geoffrey De Smet
>            Assignee: Michael Biarnes Kiefer
>
> Motivation:
> 1) Chrome has "a long-term plan to mark all HTTP sites as non-secure."
> https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html
> 2) SEO: Google/Bing penalize website (lower ranking) that use http or mix http and https.
> To do:
> - Change all absolute links on our websites _and in our user manuals_ that lead to redhat.com, jboss.org, drools.org, optaplanner.org, jbpm.org and kiegroup.org to https.
> - This includes canonical meta elements
> - This includes tabzilla.js/.css loading of images (those actually give us the mixed https and http errors in chrome's inspect tooling if you go to https://www.drools.org today)
> - This does not include external links, such as to wikipedia etc.
> Keep an eye out on google webmaster tools to verify this doesn't introduce broken links.
> Exceptions:
> - ci.optaplanner.org must be on http, because those sites don't work over https...
> Note: I've asked eng-ops to do ssl monitoring of our websites. So basically no risk of out of date certifications etc.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)