putFile/putStream API should handle HTTP 307 redirects from AWS S3

I totally get the "low level" knox API should leave this kind of handling to the client. But I wanted to suggest that the "high level" knox S3 API handle the cases where AWS S3 returns a HTTP `307` status code.

The Amazon's S3 doc says:

```
If you create a bucket using , applications that access your
bucket must be able to handle 307 redirects."
```

This happened to me when I used LearnBoost/knox#53 a few minutes after creating a new bucket in AWS to use. Once DNS is sync'd with S3, the case is likely more rare.

Obviously there are "workarounds" for this, but wanted to bring it up since knox is working pretty well for me otherwise! Thanks!

Start at the putFile and putStream API entry points and trace how they handle AWS S3 responses, focusing on HTTP 307 redirects during uploads. Confirm the behavior with a reproducible redirect case or relevant tests; done means both APIs handle the redirect rather than failing or requiring a client workaround.

Written by the indexing model from the issue text.