Mon, 27 Jul 2015 11:01:58 -0500 Sam Whited <[email protected]> wrote:
> 2) Easily match signed requests; I did an example implementation where > the server delegated storage to Amazon S3. The server would generate a > pre-signed upload URL with a limited TTL, then the client would make a > PUT to this URL. However, the headers did not match, so I had to > modify the client to add a Content-Type header which was required by > Amazon. Other headers might be required as well, and this would mean > implementaitons which use services like this would only be compatible > with certain clients Do you have any ideas how HTTP headers can be incorporated into the XEP? Because, for example, Content-MD5 header (used in Amazon S3) is also required for a receiver to be known, but there is no interaction between a sender and a receiver defined in the XEP.
