Proxy/Citation Style issue (understood and workaround found)
I am in a facility where the security proxy permits only HTTP and HTTPS.
I discovered that I could not add citation styles directly at the Zotero local application. The error message "Could not resolve ..." usually indicates a proxy setup issue. I've found no documents on how to set up proxies.
If I go to the citation library using a browser I can find the citation CSL, download it, and install it. This works without problem for independent CSLs. The dependency resolution does not work. For dependent CSLs I need to look at the CSL and go to all the parent citation CSLs in the right order and install them.
This may be a bit inconvenient but it's a viable workaround.
It would be a big help if the documentation could include network access requirements information. More and more security systems are requiring a positive access control permission list. You need to know the protocols, ports, and destination hosts that are wanted by the application. Then the security folks can add these permissions to access control lists on both workstations and proxies.
I doubt wss:// will be allowed out, so I know that some Zotero functions will not work. Documentation like that would let me know what to expect.
I discovered that I could not add citation styles directly at the Zotero local application. The error message "Could not resolve ..." usually indicates a proxy setup issue. I've found no documents on how to set up proxies.
If I go to the citation library using a browser I can find the citation CSL, download it, and install it. This works without problem for independent CSLs. The dependency resolution does not work. For dependent CSLs I need to look at the CSL and go to all the parent citation CSLs in the right order and install them.
This may be a bit inconvenient but it's a viable workaround.
It would be a big help if the documentation could include network access requirements information. More and more security systems are requiring a positive access control permission list. You need to know the protocols, ports, and destination hosts that are wanted by the application. Then the security folks can add these permissions to access control lists on both workstations and proxies.
I doubt wss:// will be allowed out, so I know that some Zotero functions will not work. Documentation like that would let me know what to expect.
https://www.zotero.org/support/kb/zotero_and_firewalls
And, Zotero does ask for more than basic browser access. It wants wss:// access too. I can see that in the error log in Zotero.
wss:// is just a WebSocket connection. That's a standard browser feature used by many websites. It operates over the HTTPS port and should work with HTTP proxies. (This is the "persistent connection" described in the privacy policy. Without it, you won't get immediate sync or translator updates, but everything else will work, and the privacy policy describes how to turn off the connection attempts.)