In EO.Total 20.0.25 can't connect through proxy. In previous version (EO.Total 19.2.91) all is ok
Tested on the same proxy.

Sent a proxy in PM

Hi,

This is just to let you know that we have posted a new build that should resolve this issue. You can download the new build from our download page. Please take a look and let us know how it goes.

Thanks!

Hi,

We did test build .33 here with the HTTPs proxy you provided and it is NOT an anonymous proxy. In fact if you modify TabbedBrowser sample application to use the proxy but provide the IP address and the port, when you load a page it will display a dialog to ask for user name and password. Are you sure you are using build .33?

Thanks!

Hi,

Are you trying to load a HTTP page while using an HTTPS proxy? In that case the proxy will be ignored since no HTTPS connection can be established for an HTTP only page.

We tested with our TabbedBrowser with this Url:

https://whatismyipaddress.com/

And it does show a different IP address when using the HTTPS proxy info you provided.

Thanks!

Hi,

We are not aware of such logic. In fact during our test, if we provide the wrong proxy information, we will get a "can not establish connection to proxy server" error.

Thanks!

You need to set Engine proxy before creating your MainWindow. For example, if you use TabbedBrowser sample application, you should set proxy in App.xaml.cs.

Hi,

We have looked into this more thoroughly and there is indeed an issue on our end. Chromium engine supports multiple proxy servers at the same time. For example, it is possible to use one proxy server for HTTP traffic and another proxy server for HTTPS traffic. There is also the notion of "fallback" proxy server in case the protocol specific proxy server does not work. On our end we only support a single proxy server, so all traffic, regardless the scheme, will go through that single proxy server. When you set proxy server through our API, we "translation" this single proxy server setting into the appropriate multiple proxy server configuration supported by Chromium. There is an issue in this translation process and it will be fixed in our next build.

We tested the fix on our end with both proxy settings you provided. Here are our findings:

1. The HTTPS proxy server you provided is in fact a HTTP proxy. So when you set ProxyInfo through our API, You must use "HTTP" type, not "HTTPS" type. If you use HTTPS type, you will get an unable to connect to proxy server error (it is possible that the proxy server only accepts HTTPs connection from certain IPs so you would not receive this error. Previously we did not receive this error due to the translation error mentioned above). The HTTP proxy does serve both HTTP and HTTPS traffic;

2. We are not able to test the SOCKS5 proxy you provided. We received error code "2" while trying to establish a SOCKS5 connection. Per SOCKS5 specification, error code 2 means "connection not allowed by ruleset":

https://tools.ietf.org/html/rfc1928

This could again be related to specific IP addresses. If you can provide another SOCKS5 proxy we will be happy to test again.

We will reply here again once the new build is available.

Thanks!

Hi,

We get the same result with the new socks5 proxy. The HTTP proxy works fine.

Unfortunately we are not in a position to fix issues in Chromium's browser engine. This is an enormous project with over 30 million lines of code and numerous things are being "fixed" daily. So it is not practical for us trying to fix things there. We would be receiving hundreds of requests asking us fixing wide range of issues every day if we were to do that. Obviously that is beyond what we can do. As a result, we generally wait for the Chromium team fix it first.

Thanks!