Configuration can be set up with the connection and/or adjusted per request.

As connection options:

conn ='', request: { timeout: 5 })

Or as per-request options:

conn.get do |req|
  req.url '/ip'
  req.options.timeout = 5

You can also inject arbitrary data into the request using the context option. This will be available in the env on all middleware.

conn.get do |req|
  req.url '/get'
  req.options.context = {
    foo: 'foo',
    bar: 'bar'

Changing how parameters are serialized

Sometimes you need to send the same URL parameter multiple times with different values. This requires manually setting the parameter encoder and can be done on either per-connection or per-request basis. This applies to all HTTP verbs.

Per-connection setting:

conn = request: { params_encoder: Faraday::FlatParamsEncoder }
conn.get('', { roll: ['california', 'philadelphia'] })

Per-request setting:

conn.get do |req|
  req.options.params_encoder = Faraday::FlatParamsEncoder
  req.params = { roll: ['california', 'philadelphia'] }

Custom serializers

You can build your custom encoder, if you like.

The value of Faraday params_encoder can be any object that responds to:

  • #encode(hash) #=> String
  • #decode(string) #=> Hash

The encoder will affect both how Faraday processes query strings and how it serializes POST bodies.

The default encoder is Faraday::NestedParamsEncoder.


Faraday will try to automatically infer the proxy settings from your system using URI#find_proxy. This will retrieve them from environment variables such as http_proxy, ftp_proxy, no_proxy, etc. If for any reason you want to disable this behaviour, you can do so by setting the global variable ignore_env_proxy:

Faraday.ignore_env_proxy = true

You can also specify a custom proxy when initializing the connection:

conn ='', proxy: '')