ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
GoLand’s integrated HTTP client inherits the operating system DNS resolver, preventing per‑project DNS configuration overrides. The SSL/TLS verification layer relies on the JVM default truststore, which cannot be customized for individual modules, leading to validation failures with self‑signed or corporate certificates. These limitations cause inconsistent
For years I was able to upload new pfx files for SSL binding on Azure App Services using the OpenSSL creation method in this Stack Overflow answer : openssl pkcs12 -export -out domain.name.pfx -inkey domain.name.key -in domain.name.crt However, doing the same now provides this error: At least one certificate is not valid (Certificate failed validation becaus
The goal is to allow Liquibase to retrieve remote changelog files via HTTPS when the server uses a self‑signed certificate and the underlying DNS records change frequently. Two documented levers exist: adding a custom truststore via the JVM system properties javax.net.ssl.trustStore and javax.net.ssl.trustStorePassword, or reducing the DNS cache TTL with the
Goal Determine whether the ignoreHTTPSErrors:true launch option in Puppeteer also suppresses SSL certificate errors for WebSocket connections initiated from a page. Current Constraints Chromium’s ignoreHTTPSErrors flag is documented to affect navigation, XHR, and fetch, but its coverage of WebSocket handshakes remains unverified. Puppeteer exposes the flag v
Goal Determine whether a running Quarkus application can recognize newly added CA certificates in its truststore without requiring a full restart. Constraints and uncertainty Quarkus relies on the default Java SSLContext unless a custom configuration is provided. The documentation states that truststore changes are not picked up at runtime, but it does not s
I am on Windows 10 using Docker to create a Debian image. However, I believe there is something wrong in the Docker Desktop, Dockerfile, or Docker command. In Docker Desktop , I have made three changes to the default configuration. Under General I have turned on Expose daemon on tcp://localhost:2375 without TLS . Under Resources > Proxies, I have http and
Goal Determine whether Splunk Enterprise 8.x automatically imports operating‑system root Certificate Authority (CA) certificates into its dedicated trust store during HTTPS forwarder ingestion. Constraints & Uncertainty Splunk stores trusted CAs in $SPLUNK_HOME/etc/system/local/ssl/ca_certs.pem and does not reference the OS trust store by default. When t
I am configuring a PostgreSQL data source in DataGrip and want strict TLS certificate validation, including hostname checking. The data source dialog offers an SSH/SSL tab with fields for a CA certificate and a server-certificate verification toggle, while the Advanced tab lets me set driver-level properties such as sslmode and sslrootcert directly. My under
Laravel HTTP Client and System DNS Resolver The goal is to understand why SSL certificate validation sometimes fails when the Laravel HTTP Client resolves a host that has been cached by the underlying PHP‑FPM DNS resolver. The Laravel HTTP Client relies on Guzzle and ultimately cURL, which in turn uses the OS resolver and the CA bundle specified by curl.cain
goland
puppeteer
docker
debian
splunk
datagrip