dwilkie/carrierwave_direct — pull request #64 by colinyoung (2013-02-17 20:40:43+00:00)
Title: Permanently fix issue #63 by making Content-Type a config option.

I still needed the Content-Type option, but I understand that if you include Content-Type in your
policy document, but don't include the corresponding field in your form, S3 will return 403's.

A better solution is to make it a configuration level option. I also added documentation
to clearly specify that you will have to add a Content-Type field to your form.