goose
goose copied to clipboard
Inspecting https certificates
While connecting a custom LiteLLM proxy i was not sure why Goose did not warn me about unknown TLS certifiate. While debugging this, I noticed there is no way to see the certificate for an API endpoint or its trust path.
Describe the solution you'd like When connecting a unknown CA it should ask, and also provide a https certificate browser so I can manually validate the connection (fingerprint).
Additional context I am not sure if it picked up my custom company CA from Windows Truststore or if it does not validate the TLS certificates (the later would be a bug and I file one when i tried it out). But this here is a enhancement feature request, not about the potential trust bug.