Proxies suddenly stopped working on Chrome (Oct 2017)

tonyh

Greetings, the proxies don't seem to work consistently. At the moment, they do not work at all. When I go to a URL in the proxy list, I am not redirected the using my proxy. Instead, I have to type in the university proxy to access the document.

I'm using the Chrome extension (Zotero Connector 5.0.24) and the latest Windows app (5.0.22). The plugin works fine, otherwise. My university library proxy is in the "configured proxies" box and the checkboxes are all enabled.
Checked: Enable proxy redirection
Checked: Automatically detect new proxies
Checked: Show a notification when redirecting through a proxy

I know the proxy and hostnames are correct. Replacing the %h in the Scheme box with the hostname and placing the URL in the browser window works.
For example:
https://www.jstor.org/stable/3033889?seq=1
http://www.jstor.org.libproxy.my-uni.edu/stable/3033889?seq=1

The advanced configuration shows the proxies as enabled.
proxies.autoRecognize true
proxies.clientChecked true
proxies.disableByDomain false
proxies.disableByDomainString .edu
proxies.showRedirectNotification true
proxies.transparent true

Ideas?

adomasven

Do you have a proxy entry for https scheme, or one for http only? If you add https://%h.libproxy.my-uni.edu/%p as an entry, add www.jstor.org in the hosts and remove it from the http scheme hostlist, does it work?

tonyh

Thanks for the response. The proxy kicked in after changing it to https, but Chrome gave me a privacy error (NET::ERR_CERT_COMMON_NAME_INVALID). Proceeding results in a 404 error.

Using http://%h.libproxy.my-uni.edu/%p does not trigger the proxy. But, https://%h.libproxy.my-uni.edu/%p triggers it with the SSL error. Is there any way to wildcard that?

adomasven

Proceeding results in a 404 error.

So what is the URL that you are taken to?

Do note that you want to keep your existing http proxy, most of the hosts saved there won't support https, but add a new proxy entry for the https scheme and only put jstor there (and the connector will gradually move other hosts to https as it discovers those supporting the protocol).

adomasven

Does https://www-jstor-org.libproxy.my-uni.edu/stable/3033889?seq=1 (note the hyphens instead of dots for the jstor hostname url) work with your proxy? If so, you should check "Automatically convert hyphens to dots in proxied hostnames" for the https proxy, which will avoid the SSL error.

dstillman

@tonyh: If you added the HTTPS proxy manually, make sure "Automatically convert hyphens to dots in proxied hostnames" is enabled for it.

dstillman

Basically, it's expected that https://www.jstor.org.libproxy.my-uni.edu would give you an SSL error. The domain you should end up at is https://www-jstor-org.libproxy.my-uni.edu (at least assuming this is a normally configured EZProxy).

When you just log in to an HTTPS site via your university site and the connector adds the proxy automatically, that setting is enabled for you.

tonyh

So what is the URL that you are taken to?
https://www.jstor.org/stable/3033889 --> https://www.jstor.org.libproxy.my-uni.edu/stable/3033889

*.libproxy.my-uni.edu is a valid cert, but it's not able to process the redirect.

After the redirect and SSL error at https://www.jstor.org.libproxy.my-uni.edu/stable/3033889, changing the URL to http://www.jstor.org.libproxy.my-uni.edu/stable/3033889? works just fine. It then establishes a non-SSL connection. This requires a manual removal of the 's'

tonyh

@adomasven @dstillman thank you! :D That fixed it. It works as expected.