Some of the titles were inconsistent in capitalization.

Fixes the following warning shown by JRuby 9.1.6.0:

> gems/paperclip-5.1.0/lib/paperclip/storage/filesystem.rb:49: warning: `&' after local variable or literal is interpreted as binary operator even though it seems like argument prefix

Fix Travis CI

Thanks for the tip, @brendon!
https://github.com/thoughtbot/paperclip/pull/2331#issuecomment-262910522

Otherwise cucumber doesn't load development dependencies.

- Updates cucumber (https://github.com/cucumber/gherkin2/issues/320#issuecomment-139572490)
- Removes `bundle exec` from commands ran in cucumber steps
- Simplifies framework_major_version (we can assume it always is 4 or
  higher)
- Inline unneeded methods
- Fix some Ruby warnings

* Remove old Tempfile tests from Thumbnail spec
* Move Tempfile tests to tempfile_spec.rb

Fix typo in README

s3_permissions can no longer be a symbol. Must be a string.
Providing a string causes hard to debug errors in AWS.

[fixes #1943]

header was changed recently (https://github.com/thoughtbot/paperclip/commit/5202acbf4b642230bef71a8dd534bcca11fb4373#diff-04c6e90faac2675aa89e2176d2eec7d8L740), but link was not and now it's broken

Allows `s3_host_alias` to be set to CDNs which support S3 Bucket prefix.

[fixes #2287]

Bug introduced in 1c7d7f66

Per https://github.com/thoughtbot/paperclip/commit/1c7d7f66ceea27cfe604e3a13c2eb87df217d13a#commitcomment-18765681 request

Rebased #2120 to master.
Paperclip duplicates the original files quite a lot as part of its validation process. (#1642, #1326).
When uploading large files (several hundred megabytes to gigabyte range), this becomes a problem: The web server will be busy creating 3 - 4 duplicates on disk, while the app (and potentially the user) are waiting for the upload operation to complete.
This pull request introduces hard links instead of ```FileUtil.cp``` where possible to keep the logic as-is but save time and disk space.

[Amazon S3 Transfer
Acceleration](http://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html)
enables fast, easy, and secure transfers of files over long distances
between your client and an S3 bucket. And
[aws-sdk](https://github.com/aws/aws-sdk-ruby) has allowed us to enable
this feature in version 2.3.0 (more detail is
[here](https://github.com/aws/aws-sdk-ruby/pull/1163)).

You can now pass a configuration option (:use_accelerate_endpoint) when
config Paperclip with S3. You can enable the [Amazon S3 Transfer
Acceleration](http://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html)
by set this option:
```:use_accelerate_endpoint => true```

[fixes #2291]

* correct S3 specs to use the correct keys in the s3_credentials hash
* S3 tests work with a region that requires s3_domain_url

[fixes #1985]

Adapters now accept an options parameter, that currently specifies
the type of hash digest to use.  The default value remains MD5, but
can be specified to be any OpenSSL-supported digest.  The specs are
modified to reflect that.

The task just reassigns all of the attachments, thereby regenerating
their fingerprints.

* ignore invalid content-disposition header

[fixes #2283]

Fix typo.

Progress on https://github.com/thoughtbot/paperclip/issues/2071.

[closes #2282]

[ci skip]

[closes #2155]

Adds a Code Climate configuration enabling Fixme, Rubocop, and
Duplication.

The Code Climate RuboCop engine uses a newer version of RuboCop than the
current Hound config, so .hound.yml was modified to work for both. The
only notable change was removing PreferredHashMethods because there is
no syntax for that cop that works with bout Hound and Code Climate.

[ci skip]

Update NEWS file.

[ci skip]

* Add default `content_type_detector` to `UploadedFileAdapter`

[fixes #1314]
[ci skip]

Default `s3_protocol` used to be `http` when `:s3_permissions` are
`:public_read` (default), and `https` when `:s3_permissions` are
anything else.

With an empty String as default, if the page is served over HTTPS,
attachment URL will be HTTPS, and if the page is served over HTTP,
attachment url will be HTTP.

`public-read` is an authorization concept, independent form the
encryption of the HTTP connection used to read the file. As such, the
one shouldn't define the other.

[fixes #2038]