OCSP check failed against windows blob storage

Nobody has claimed this yet.

I am using ocsp 1.2.0 and latest of asn1.js-rfc5280. However, ocsp check failed with error `Invalid signauture` when checking against azure blob storage(while it succeed for amazons s3). So I am wondering what is wrong, and also, is there anyway to turn on logging to further troubleshooting the issue.

I wrote a simple javascript to reproduce the issue. Note, check failed on windows.net, but succeed for s3 endpoint.
```
const tls = require('tls');
const ocsp = require('ocsp');
const rfc5280 = require('asn1.js-rfc5280');

const options = {
host: "2srsfctest1stage000.blob.core.windows.net",
//host: "s3-eu-west-1.amazonaws.com",
port: 443
};

const socket = tls.connect(8000, options, function(){
cert = socket.getPeerCertificate(true);
var issuer = cert.issuerCertificate;
cert = cert.raw;
try {
cert = rfc5280.Certificate.decode(cert, 'der');

if (issuer) {
issuer = issuer.raw;
issuer = rfc5280.Certificate.decode(issuer, 'der');
}
} catch (e) {
console.log(e);
}

ocsp.check({
cert: cert,
issuer: issuer
}, function(err, res){
if (err)
{
console.log(err);
}

if (res)
{
console.log(res);
}
})
});
```

Start by running the provided JavaScript reproduction with the Azure Blob Storage host and the S3 host for comparison, focusing on the tls connection and ocsp.check call. Investigate the reported “Invalid signauture” result and whether the ocsp package exposes logging; done means explaining the endpoint difference or identifying the needed diagnostic or fix.

Written by the indexing model from the issue text.