GitLab

In the long-ago times, OCSP stapling at the TLS layer was only enabled
if the certificate verification layer would be able to use these OCSP
responses as part of verification - which was true on Windows > XP and
'bleeding edge' versions of NSS at the time. However, this conditional
enabling at the TLS layer has been long replaced with unconditional
enabling, to support both Certificate Transparency (~2015) and
Expect-Staple experiments.

As a result, it's no longer necessary to report the platform
capabilities to enable this optimization.

BUG=none
TBR=mmenke@chromium.org, bartfab@chromium.org

Change-Id: Ia3c0d4cb161da47738ccb287a8286d6ce6248162
Reviewed-on: https://chromium-review.googlesource.com/1117034
Commit-Queue: Ryan Sleevi <rsleevi@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570862}