I'm closing this ticket for now; this system is generally intended for bug reports and feature requests. For more general-purpose support, I would encourage you to join the vufind-general and/or vufind-tech mailing lists, as described here under Community Support:

Demian Katz
added a comment - 22/Jan/18 11:34 AM You should be able to configure your proxy server in this section of config.ini:
https://github.com/vufind-org/vufind/blob/master/config/vufind/config.ini#L1109
I'm closing this ticket for now; this system is generally intended for bug reports and feature requests. For more general-purpose support, I would encourage you to join the vufind-general and/or vufind-tech mailing lists, as described here under Community Support:
https://vufind.org/vufind/support.html
Please let me know if you need further assistance -- I'm always happy to help!

A quick review of the code suggests that (even back in version 2.4) both the Google and Amazon cover handlers were using VuFind's central HTTP service, which in turn should be respecting the proxy settings in config.ini.

There have been some adjustments to the proxy logic in newer releases of 2.4. Do you have the ability to test with a newer release to see if that offers different results?

Demian Katz
added a comment - 23/Jan/18 1:05 PM A quick review of the code suggests that (even back in version 2.4) both the Google and Amazon cover handlers were using VuFind's central HTTP service, which in turn should be respecting the proxy settings in config.ini.
There have been some adjustments to the proxy logic in newer releases of 2.4. Do you have the ability to test with a newer release to see if that offers different results?
Are you using a non-default HTTP adapter at https://github.com/vufind-org/vufind/blob/release-2.4/config/vufind/config.ini#L800 ? That could make a difference, too.