|
|
Rank: Advanced Member
Groups: Member
Joined: 1/12/2015
Posts: 85
|
I'm going to use the following terminology to indicate proxies:
IP1-C1
IP2-C2
IP1-C3
An IP with the same number after it means the IP and port number are the same. C is the credentials (username/password). So IP1-C1 and IP1-C3 have the same IP and port but different credentials. And IP2-C2 is different IP/port and different credentials.
After successfully setting the proxy and browsing to a new page with IP1-C1 and then setting the proxy to IP1-C3 and loading another page, it is still actually using IP1-C1 instead of IP1-C3.
I've also tried the following sequence with the same browser instance:
1. Changing proxy to IP1-C1 loads with IP1-C1 (good)
2. Changing proxy to IP2-C2 loads with IP2-C2 (good)
3. Changing proxy to IP1-C3 loads with IP1-C1 (bad)
I am ensuring that I wait long enough after switching proxies to ensure previous page loads complete. I am currently using build 2023.0.83.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,245
|
Hi,
This may not be a proxy issue --- it maybe an authentication/caching issue since the lower level connection would be the same for C1 and C3 because C1 and C3 has the same IP and port. After the proxy is changed from C1 to C3 (or C3 to C1) and the page is reloaded, the new user name/password will only be used if the page does indeed requires re-authentication. If that's not the case then the new user name/password would not take effect.
Nevertheless we have sent you a new build that is based on a much newer Chromium engine. You can try that build and see if it works for you. If it still does not work for you, you can PM us with the proxy info and we will try to debug into the browser engine here to see what we can find.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 1/12/2015
Posts: 85
|
I agree. I think that is the problem. The new version didn't work. I can't send you the proxy info because I'm using a local proxy. However, I'm pretty sure the issue can be fixed. I know it's been done for CEF browser.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,245
|
Do you have any additional information about this issue in CEF? We can look into their code changes which would help us to identify/resolve this issue.
|
|
Rank: Advanced Member
Groups: Member
Joined: 1/12/2015
Posts: 85
|
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,245
|
Hi,
We will add WebView.ClearAuthCache in our next build that will eventually call Chromium's NetworkContext::ClearHttpAuthCache method. We will reply here again once the new build is avaiable so that you can try it out. Once the method is added, you would need to call this method explicitly when you change proxy.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 1/12/2015
Posts: 85
|
Thank you for the update. I'm just curious why Chromium's method won't automatically be called when the new proxy is set? Also, do you have a time estimate of when the new build would be ready?
|
|