红色 https 无故打叉 (Apache + mod_ssl)
Red https with cross without reason (Apache + mod_ssl)
我刚刚添加了带有签名证书的 mod_ssl，但我不明白为什么 Google chrome 将我的连接标记为不受信任
截图：
尽管另一个网站具有几乎相同的详细信息，但是 Google chrome 并未将其标记为不受信任：
有人可以帮助我吗，为什么 google chrome 将我的网站标记为不受信任？
编辑 1（添加证书信息）
每 Google's note on SHA-1 deprecation,
Sites with end-entity certificates that expire on or after 1 January 2017, and which include a SHA-1-based signature as part of the certificate chain, will be treated as “affirmatively insecure”. Subresources from such domain will be treated as “active mixed content”.
The current visual display for “affirmatively insecure” is a lock with a red X, and a red strike-through text treatment in the URL scheme.
我刚刚添加了带有签名证书的 mod_ssl，但我不明白为什么 Google chrome 将我的连接标记为不受信任
截图：
尽管另一个网站具有几乎相同的详细信息，但是 Google chrome 并未将其标记为不受信任：
有人可以帮助我吗，为什么 google chrome 将我的网站标记为不受信任？
编辑 1（添加证书信息）
每 Google's note on SHA-1 deprecation,
Sites with end-entity certificates that expire on or after 1 January 2017, and which include a SHA-1-based signature as part of the certificate chain, will be treated as “affirmatively insecure”. Subresources from such domain will be treated as “active mixed content”.
The current visual display for “affirmatively insecure” is a lock with a red X, and a red strike-through text treatment in the URL scheme.