Hi,
We have looked into this issue. Here are our findings:
1. The "Secure" option in the configuration dialog you use to configure proxy in Chrome (as well as in IE since the dialog is provided by the system) is
NOT the same as "https" proxy type.
The "Secure" option in this dialog means "use this
HTTP proxy for secure connection". In another word, you can have two HTTP proxies, one for non-secure connections (HTTP) and one for secure connections (HTTPS). Note that for both secure and non-secure connection, the proxy type is HTTP. There is a special command in HTTP proxy that allows it to support both HTTP and HTTPS, but the key is, in both cases, the proxy type is HTTP, not HTTPS. This seems to be the only type of proxy your proxy server supports. This is why only the HTTP proxy type works for you because this is the only one you have;
As a side note, we do not support different proxies servers for secure and non-secure connections.
2. The HTTPS proxy type in our ProxyInfo is a different type of proxy and it is not commonly used. While we have the source code (from Chromium project), even we are not familiar with the details. Setting ProxyInfo's ProxyType to HTTPs is equivalent to this option in Google Chrome:
https://www.chromium.org/developers/design-documents/secure-web-proxyAs you can see this is completely different than setting the "Secure" option in the proxy configuration dialog.
3. We are not able to use your SOCKS5 proxy server through the proxy configuration dialog either. So it appears that your proxy server does not support this type of proxy.
Hope this helps. Please feel free to let us know if you still have any more question.
Thanks!