Avoid proxy/orcid clash -- maybe proxy only some urls on a host?

Unfortunately, as some of the big online publishers consolidate their online presences under a single hostname (e.g. www.cambrdige.org) I've started to run into more and more issues with the zotero proxy scheme. I really love automatically proxying the pages displaying journal articles but then when I go to submit an article,, login to do a review or or do something else on those sprawling websites I run into problems. For instance, login via orcid breaks -- indeed probably must break to remain secure -- when the site being logged into is automatically proxied.

This is pretty annoying so I'm wondering if there is any workaround. Ideally, I could somehow liimit the automatic proxy to only certain urls on the host, e.g. www.cambridge.org/core/journals/**. I mean, I guess the ideal solution would make firefox treat the proxied and original host as the same domain for cookies and then exclude things like orcid login endpoints -- but that seems crazy hard and I'm hoping for some easy way to solve this problem.

Thoughts?
  • This is an interesting question and I think I see where the clash is happening in general, but I am not sure how Zotero is involved in the story. Can you describe your workflow, maybe as a list of steps?
  • Zotero's proxy integration will direct everything from an included hostname through the proxy schema. I see how that might cause issues when combined with other authentication (like ORCID).

    I don't think I have seen this -- when I review for Cambridge, e.g., that's through editorialmanager URLs, but I can see it happening.
  • Some example (unproxied) URLs here would be helpful.
Sign In or Register to comment.