jwinterfeld

@tw2113 we resolved the issue without code modification. After investigating the code we found the filter algolia_http_client_options in this file: https://github.com/WebDevStudios/wp-search-with-algolia/blob/main/includes/factories/class-algolia-http-client-interface-factory.php

We resolved it by declaring a function in the theme functions.php file:

if (! function_exists('dur_algolia_http_client_options')) :
  function dur_algolia_http_client_options($options)
  {

    $options['CURLOPT_PROXY'] = WP_PROXY_HOST . ':' . WP_PROXY_PORT;

    return $options;
  }
  add_filter('algolia_http_client_options', 'dur_algolia_http_client_options', 10, 1);
endif;

My recommendation is to update the docs and explain the filter instead of modifying the plugin. What do you think?

Thanks Michael.

I did some investigation and believe we should extend the SearchConfig::create method (reference: SearchConfig.php#L15) to accept “hosts” and “headers” as parameters. Does that make sense to you?

Related Algolia Docs:
– https://www.algolia.com/doc/libraries/php/v3/customize/#use-a-custom-host
– https://www.algolia.com/doc/libraries/php/v3/customize/#add-http-headers-to-every-request