Configure Proxy Routes in Ruby Geocoder

A Rails address lookup normally leaves from the application process that runs Geocoder. A proxy configured in the developer's browser is not evidence that a web worker or background job uses that route.

Geocoder exposes proxy settings in its configuration. In the application's initializer, an explicit endpoint can be supplied for both destination protocols:

Geocoder.configure(
  http_proxy: 'proxy.example.net:8080',
  https_proxy: 'proxy.example.net:8080'
)

For this Net::HTTP lookup path, Geocoder chooses http_proxy or https_proxy according to the lookup protocol and parses the endpoint into host, port and optional credentials. Keep the setting consistent with the lookup backend and Geocoder version actually in use. When an allowed public-provider lookup needs no proxy account, the HTTP proxy list can supply candidate host:port values for this HTTP intermediary.

Configure the process that performs the work. If geocoding runs in a separate job worker, changing an initializer in the web deployment does not update an already-running worker's configuration. Reload or restart the appropriate process through the application's normal deployment procedure. For lookups executed by Sidekiq, check the actual worker process and its client inputs.