Enabling HTTP/2 on Tomcat 10: A Practical Step‑by‑Step Guide
Configure Tomcat 10 for HTTP/2 by adding an NIO2 HTTPS connector with ALPN support, validate with curl and DevTools, and recover by reverting to the backup if necessary.
Loading…
ReadMeFeed / Community knowledge
#ssl
Real questions. Useful conversations. Find the people who know your stack.
java
tomcatQNetworkAccessManager: Asynchronous HTTP in Qt
Simplify concurrent HTTP calls in Qt with QNetworkAccessManager—handle multiple requests, SSL, redirects, and incremental data—all without manual threads.
qtDiagnosing OpenSSL TLS Handshake Failures: Symptoms, Checks, and Fixes
Learn how to recognize common OpenSSL TLS handshake failures, identify their likely causes, run ordered verification steps, apply targeted fixes, and know when to escalate.
opensslWhy does DBeaver fail to validate a PostgreSQL server's SSL certificate when the hostname resolves via DNS, and how can I configure a custom truststore to fix it?
When connecting to a PostgreSQL instance over TLS using DBeaver, the client sometimes rejects the server's certificate despite the certificate being valid and trusted by the system Java keystore. The issue appears to be related to DNS resolution of the host name used in the connection string, which may cause a mismatch between the certificate's subject alter
dbeaverLimits of SQLAlchemy's SSL hostname verification across database drivers
Goal: Determine whether SQLAlchemy offers a unified mechanism to enforce hostname verification for SSL/TLS connections when using different database backends such as PostgreSQL (psycopg2) and MySQL (PyMySQL/mysqlclient). Constraint: SQLAlchemy passes SSL-related keys in connect_args directly to the underlying DBAPI, which interprets them differently; there i
sqlalchemy
mysqlHow can I configure Git to use a custom DNS resolver and a specific CA certificate for HTTPS remotes behind an intercepting proxy?
When cloning or fetching from an HTTPS repository through a corporate proxy that performs SSL interception, Git sometimes fails to verify the server’s certificate because the proxy presents its own CA‑signed certificate. At the same time, the internal DNS used to resolve the repository host differs from the system DNS, causing Git to connect to the wrong add
gitDBeaver SSL connection fails with hostname mismatch after trusting server certificate
When configuring a DBeaver connection to use SSL with a self‑signed or private‑CA certificate, the user can enable the “Trust server certificate” option or import the certificate into the connection‑specific truststore. The intended goal is to allow the connection to succeed despite the certificate not being present in the Java default truststore. However, i