ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Determine how RabbitMQ handles hostname lookups when clients use DNS SRV records for cluster discovery and whether it refreshes those lookups after a connection is established. Constraints RabbitMQ resolves hostnames via the operating system resolver; it does not natively support SRV records. Once a client connects, the broker does not re‑resolve the ho
Limits of TLS certificate validation in Consul DNS proxy for upstream DNS‑over‑TLS The Consul DNS proxy can forward queries to external DNS resolvers using DNS‑over‑TLS (DoT). Documentation states that the proxy does not perform TLS certificate validation on the upstream server; the client must handle verification. This leaves an unresolved decision about wh
Goal Ensure that OpenSSL’s ASN.1 TIME parsing consistently translates timezone offsets into a predictable representation for applications that convert the returned time to local civil time. Constraints and uncertainty OpenSSL currently returns the time as a time_t value interpreted as UTC, discarding any timezone offset present in the ASN.1 TIME field. Some
Administrators want Redis to reject TLS connections when the client certificate does not match the hostname used to reach the server, ensuring that a certificate issued for one service cannot be reused for another. Currently, with tls-auth-clients set to yes, Redis validates the certificate chain and expiration but relies on the underlying OpenSSL library to
When building a NestJS application that relies on the injected HttpService for outbound HTTPS calls, I need to ensure that all requests use a specific DNS resolver (e.g., an internal DNS server) and optionally relax certificate validation for internal services with self‑signed certificates. The HttpService is a thin wrapper around Axios, which ultimately use
Goal Investigate how DNS resolution and TLS certificate validation behave when Capacitor HTTP requests are routed through the embedded Web View versus a native HTTP client, and determine the impact on app reliability when system DNS or certificate stores change. Constraints & Uncertainty Capacitor’s default HTTP plugin uses the Web View’s networking stac
In a k3os environment, CoreDNS operates as a system-wide addon managed by the kube-controller. When deploying on edge nodes with specific upstream DNS providers, resolution often fails because the node's resolv.conf conflicts with the CoreDNS configuration in the k3s manifest. Furthermore, because k3os utilizes a read-only root filesystem by default, injecti
The goal is to execute a k6 test that writes metrics to an InfluxDB endpoint over HTTPS in a production environment while keeping TLS certificate verification enabled, rather than disabling it with --insecure-skip-tls-verify . By default, k6 relies on the Node.js TLS implementation and the system's root CA bundle to validate the InfluxDB server's certificate
In Qt 6.x, the Qt Network module utilizes platform-specific backends such as OpenSSL on Linux and Schannel on Windows to handle TLS handshakes. While core certificate validation is generally managed through the QSslError signal, the behavior regarding OCSP stapling remains inconsistent across these environments. When a server provides an OCSP staple response
consul
openssl
redis
nestjs
capacitor
k6