Issues importing from pubs.acs.org using University home proxy

jnmurphy
1. I am using Zotero (4.0.26.4 - fully updated) with Google Chrome (43.0.2357.81 m - fully updated) with Zotero Connector (4.0.26 - current version) on Windows 8.1 (fully updated) and trying to download bibliographic data to the reference manager.

2. I am using the University of Alberta proxy for access from home. e.g. http://pubs.acs.org.login.ezproxy.library.ualberta.ca/doi/abs/10.1021/ma9002903

3. Using the proxy address, I have no problem downloading bibliographic data from every other major publisher's website, such as Wiley, Nature, IOP, Elsevier, or PLOS. Everything works as usual.

4. However, when I access ACS publications via the proxy, and click the reference manager's icon, the small window showing that it's downloading the reference pops up, but without all of the usual items; when I check in Zotero no entry is created in the Zotero database (not anywhere!)

4b. ACS has a direct link which works fine: I can download the *.ris file and import that manually

5. When I access ACS publications without the proxy, and click the reference manager's paper icon, it shows this (as per normal), and an entry is created in the Zotero database. e.g. just http://pubs.acs.org/doi/abs/10.1021/ma9002903

6. Using Firefox with its Zotero Connector works fine; no problems.

So something is amiss here, and I have no clue what it is. I appreciate your time and patience in providing assistance in understanding and dealing with the problem.

Jeffrey
  • adamsmith
    So to summarize, the issue is 4.) -- when trying to import from ACS via the URL bar icon in Chrome and going through a proxy, import fails "silently" (i.e. no error message, no import). Correct so far?

    Three questions
    1) does this work with
    https://pubs.acs.org.login.ezproxy.library.ualberta.ca/doi/abs/10.1021/ma9002903
    (i.e. using https instead of http?

    2) What does it say when you hover over the Zotero URL bar icon for that page?

    3) Could you provide a debug ID from the Chrome connector that covers such a failed import:
    https://www.zotero.org/support/debug_output#zotero_connectors_chrome_and_safari
  • jnmurphy
    Hi Adam,

    Yes, that is correct so far.

    1. No, it does not work with HTTPS, as the page returns "404 Not found".

    2. Hovering on the Zotero URL bar icon, it says "Save to Zotero (ACS Publications)". After clicking it, the pop-up window (bottom right) says, "Saving to <folder name>"

    3. I just submitted it: D353900389
  • jnmurphy
    To compare, I also recorded what the Chrome import looked like with just the pubs.acs.org domain; no proxy. D1680558946
  • adamsmith
    @Dan - could you check the debug?
  • dstillman
    (3)(+0000008): Translate: Creating translate instance of type import in sandbox

    (4)(+0000015): Translate: Binding sandbox to http://pubs.acs.org.login.ezproxy.library.ualberta.ca/doi/abs/10.1021/ma9002903

    (4)(+0000003): Translate: Parsing code for RIS

    (3)(+0000011): Translate: Beginning translation with RIS

    (3)(+0000006): Translate: Translation successful

    (5)(+0000003): Translate: Running handler 0 for done

    (3)(+0000002): Translate: Translation successful

    (5)(+0000003): Translate: Running handler 0 for done
  • adamsmith
    @aurimas - does ACS work for you with proxy on Chrome? I don't really see why we're not getting the RIS.

    @Dan - could you add the POST request a couple of lines above that?
  • dstillman
    HTTP POST doi=10.1021%2Fma9002903&downloadFileName=achs_mamobx42_4896&include=abs&format=refman&direct=on&submit=Download+article+citation+data to http://pubs.acs.org/action/downloadCitation
  • aurimas
    edited June 5, 2015
    This may fix itself if we correct the target regexp to not match the proxy. (Though we should also use relative URL)
  • aurimas
    @jnmurphy this should be fixed now. Can you update your translators via Preferences -> General -> Update Now, restart browser, and try again? Let us know if this is still not working.
  • jnmurphy
    @aurimas @Dan: It works perfectly now -- I've updated and restarted, as directed, and it works with the proxy now. Thank you for fixing this so quickly.
    Here's the output logging ID, to compare if necessary: D1726598111
    Thanks again!!

    Jeffrey
Sign In or Register to comment.