jubos/fake-s3

The issue only required modifying the Allowed-Headers,
but it seemed strange to add the ability to control
that one without being able to control the others

- Current behavior without added flags is unnaffected
- No existing assertions are changed
- Added assertions to demonstrate control of CORS Headers

This library has long since been deprecated, and this will remove a bunch of spurious warnings in the test output.

…rwritten with "attachment" (#211)

Thanks!

* add delete objects

* add delete objects

* add delete objects

* Update gitignore

…r. (#141)

* Change redirect code from 307 to 303

This matches the behavior of the real S3.

The difference between 303 and 307 is significant. The HTTP 1.1 standard
says that a 307 indicates the request should be repeated using the same
method and post data, whereas a 303 always indicates a GET request.

This causes a bug when success_action_redirect is specified: a POST to
Fake S3 will subsequently POST to success_action_redirect instead of
GET as expected.

* Append object params to success_action_redirect

S3 appends these params so that the success page can reference the newly
uploaded object. This is required to make tools like Shrine work.

…ny longer