Per‑project DNS and SSL configuration missing in GoLand HTTP client

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 behavior across team members and obscure troubleshooting of proxy‑related NTLM handshakes.

Is per‑project DNS override supported in the IDE?

Can the HTTP client be configured to use a custom truststore per module?

Does the lack of per‑project SSL settings affect CI pipelines?