Hi Jerome, Just tried implementing the AWS challenge scheme as you suggested and it works great!
The only problem I seem to have is with 'empty' requests: When there is no entity representation in the request the Content-type is set to a default value of 'application/x-www-form-urlencoded' for all request methods except 'PUT' - in which case the header is left out!!! I'm aware that the problem lies with the HttpURLConnection class. But, if you have any suggestions for a way to remove (or explicitly set) the content-type I would very much like to hear it! So far the rule stated above seems to hold up so I am able to construct the AWS credential correctly. It just seems like bad programming style to have to depend on some fairly undocumented default value. - Mikkel
