Som-Som

The reason I put this one right after Gorilla/Mux is that this framework is heavily based on Gorilla/Mux. In most cases it can be used as a drop in replacement...

@Aneurysm9 > The `B3` propagator intentionally does not inject the `x-b3-parentspanid` field as [the specification forbids it](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/context/api-propagators.md#b3-inject). Parent span is not propagated. That is fine. But client span is to...

There is a [nice article](https://akshayranganath.github.io/OCSP-Validation-With-Openssl/) explaining how to check OCSP with OpenSSL, and OCSP ULR being in the certificate. Still, we may need that aforementioned OCSP URL setting, in case...

Note that in Go 1.19 `x509.ParseCRL` is replaced by `x509.ParseRevocationList`.

An article on how cert revocations are performing on the public internet: https://www.ssl.com/blogs/how-do-browsers-handle-revoked-ssl-tls-certificates/

Even if redirection is allowed client's `HTTPS()` settings must be applied. As it is implemented in `Do()`, that must work automatically.

Since `otelhttp.NewTransport` transport is used at `http.Client` that does the instrumentation, we do not really need to care about span and its lifespan. So, this ticket is the other way...