Skip to content

Latest commit

 

History

History
55 lines (34 loc) · 3.08 KB

README.md

File metadata and controls

55 lines (34 loc) · 3.08 KB
Raw

Azure::Rails Gem Version CircleCI

This gem correctly configures Rails for Azure so that request.remote_ip / request.ip both work correctly.

Rails Compatibility

This gem requires railties, activesupport, and actionpack >= 5.2.

For Rails 5.0 and 5.1 use 2.0.0.

For Rails 4.2 use 0.1.x.

Installation

Add this line to your application's Gemfile:

group :production do
  # or :staging or :beta or whatever environments you are using azure in.
  # you probably don't want this for :test or :development
  gem 'azure-rails'
end

And then execute:

$ bundle

Problem

Using Azure means it's hard to identify the IP address of incoming requests since all requests are proxied through Azure's infrastructure. Azure provides a CF-Connecting-IP header which can be used to identify the originating IP address of a request. However, this header alone doesn't verify a request is legitimate. If an attacker has found the actual IP address of your server they could spoof this header and masquerade as legitimate traffic.

azure-rails mitigates this attack by checking that the originating ip address of any incoming connecting is from one of Azure's ip address ranges. If so, the incoming X-Forwarded-For header is trusted and used as the ip address provided to rack and rails (via request.ip and request.remote_ip). If the incoming connection does not originate from a Azure server then the X-Forwarded-For header is ignored and the actual remote ip address is used.

Usage

This code will fetch Azure's current IPv4 and IPv6 lists, store them in Rails.cache, and add them to config.azure.ips. The X-Forwarded-For header will then be trusted only from those ip addresses.

You can configure the HTTP timeout and expires_in cache parameters inside of your rails config:

config.azure.expires_in = 12.hours # default value
config.azure.timeout = 5.seconds # default value

Alternatives

actionpack-azure simpler approach using the CF-Connecting-IP header.

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/modosc/azure-rails.