You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proxying to a service using SSL with a self-signed certificate results in an error: "Proxy settings are NOT ENABLED". That's misleading, given that proxying a service and using an HTTP proxy for outbound requests are unrelated. The actual error is an SSLPeerUnverifiedException, thrown from httpclient.execute() in ClientExecuteProxy. Unfortunately, that gets caught and Mockey reports a problem with the proxy configuration. The SSL error is logged, but it's easily missed...
At minimum I'd like to see the problem surfaced in the service history (rather than mis-diagnosed as a problem with the HTTP proxy config). Better yet would be a way to allow self-signed certs, as Mockey is currently unusable in this situation (and I don't have control over the remote service to either allow HTTP requests or replace the self-signed cert).
The text was updated successfully, but these errors were encountered:
Proxying to a service using SSL with a self-signed certificate results in an error: "Proxy settings are NOT ENABLED". That's misleading, given that proxying a service and using an HTTP proxy for outbound requests are unrelated. The actual error is an SSLPeerUnverifiedException, thrown from httpclient.execute() in ClientExecuteProxy. Unfortunately, that gets caught and Mockey reports a problem with the proxy configuration. The SSL error is logged, but it's easily missed...
At minimum I'd like to see the problem surfaced in the service history (rather than mis-diagnosed as a problem with the HTTP proxy config). Better yet would be a way to allow self-signed certs, as Mockey is currently unusable in this situation (and I don't have control over the remote service to either allow HTTP requests or replace the self-signed cert).
The text was updated successfully, but these errors were encountered: