ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Problem InfluxDB OSS 2.x serves HTTPS using a certificate whose Subject Alternative Name (SAN) may not include the DNS name used by the client. When the client resolves the host via DNS and initiates a TLS handshake, the hostname verification fails and the connection aborts before any data is exchanged. This manifests as a generic “connection error” or timeo
Couchbase SDKs use couchbases:// for encrypted connections and validate the server certificate chain and hostname during the TLS handshake. The uncertainty is which hostname the SDK compares against the certificate's Subject Alternative Names (SAN) when the address used for bootstrap differs from the addresses the cluster advertises later. Several conditions
Quasar CLI v2+ uses Vite as the dev server. HTTPS is configured via devServer.https in quasar.config.js as a boolean for auto-generated self-signed certs or an object with key / cert / ca paths. devServer.proxy forwards API requests to backend services. Certificate validation for proxied HTTPS requests is performed by Node.js using its built-in trust store.
Goal Determine the exact circumstances under which Firefox, with DNS over HTTPS (DoH) enabled, silently reverts to the system resolver when encountering a certificate validation error during a DoH request. Current Ambiguities Firefox defaults to the system DNS but may override this when DoH is active. A failed TLS handshake on a DoH query can be interpreted
Goal We want to issue an HTTPS request to a server identified by an IP address while setting the Host header to a domain that has a valid TLS certificate. The request should perform DNS resolution via a custom resolver so that the domain maps to the desired IP, and the TLS handshake should validate the certificate against that domain. Constraints Using the d
Integration Boundary LabVIEW’s built-in HTTPS client on Windows delegates TLS certificate validation to WinHTTP, which consults the Windows system certificate store. The client also exposes a Certificate Store property that can override the system store with a custom CA list. The integration point between the LabVIEW runtime and the OS trust store is not ful
FileZilla stores user‑trusted certificates in its certificate manager, yet when connecting to an FTPS server that presents a self‑signed certificate the client still prompts for validation on each new session, even though the certificate is marked as trusted. The goal is to determine whether the client should automatically skip hostname verification for such
Zig's std.tls implementation relies on the mbedTLS backend for handling TLS connections. While the library provides mechanisms for certificate verification, there is a discrepancy in how root certificates are handled across different target operating systems. Currently, the default trust store may not automatically incorporate platform-specific root certific
On Arduino boards using WiFiNINA, WiFiS3, or Ethernet with Arduino_SSLClient, DNS resolution can succeed while the TLS handshake rejects the server certificate. The supported path separates name resolution from secure client initialization, leaving the exact validation behavior dependent on the installed board package and library version. The unresolved deci
couchbase
quasar
ktor
labview
filezilla
zig