Use self-hosted solution for OCSP stapling check

[na--]

As seen in https://github.com/loadimpact/k6/issues/537#issuecomment-374920627 and https://github.com/loadimpact/k6/pull/1274, the current solution for testing OCSP statuses is very sub-optimal. Ideally, we shouldn't depend on any external resources to run the test...

[mstoykov]

This test now started failing on GHA for no apparent reason, likely due to wikipedia gettign resolved to something different.

I have disabled the test fo now so that CI works

[monteiro-renato]

Hey @mstoykov,

Do you have any updates here?

I tried to follow the tutorial here: https://grafana.com/docs/k6/latest/using-k6/protocols/ssl-tls/online-certificate-status-protocol-ocsp/ but it doesn't look like this is working as intended.

This is what I get if I am getting in the console.log

INFO[0000] {"produced_at":0,"this_update":0,"next_update":0,"revoked_at":0,"revocation_reason":"","status":"unknown"}  source=console

[mstoykov]

From my experience, most sites stopped doing OCSP stapling. Including everything we used to test. I just tried and cloudflare.com is the only thing I tried that has ocsp and the code works with it.

So in your case I will expect that the site you are testing with just doesn't have OCSP stapling :(