(Noticed this while doing JDK-8328638 backports)
JDK-8328638 introduced a new boolean option, `com.sun.security.ocsp.useget`. We use the usual `Boolean.parseBoolean` to convert it from String to boolean value, which works correctly for `false` and `true` as boolean values. However, any string that is not `true` would be treated as `false`. Which means that if users mistype the value, they would not get the default behavior pre-JDK-8328638, but rather a fallback, non-default behavior.
It would be preferable to validate the option range a bit better, and default to the correct value on any error.