2 ms·
The site isn't broken in Firefox or Chromium. Maybe the behavior that the changes to Chrome signal a willingness to break the open web.
by brudgers 10y ago
The site isn't broken in Firefox or Chromium. Maybe the behavior that the changes to Chrome signal a willingness to break the open web.
- okket 10y agoIt is clearly a violation of the TLS RFC 5246 [1], page 47, Server Certificate -> certificate_list. You may only omit the root, but otherwise must supply all parts of the certificate chain. [1] https://tools.ietf.org/html/rfc5246 https://tools.ietf.org/html/rfc5246
- brudgers 10y agoChrome is, in turn, in violation of the robustness principle: https://en.wikipedia.org/wiki/Robustness_principle https://en.wikipedia.org/wiki/Robustness_principle