Yep, exactly. However, I also wanted to address all the content metadata in general. But. That's a lot of work and affects multiple providers. Some choices: 1. Refactor properly and change the provider/api code as needed. Remove default behavior. Treat all headers the same way, maybe. Get rid of how content- headers work now. Hope for the best. 2. Keep the default behavior but add some options that allow us to modify that behavior from a provider/api, so not all providers are affected. For example a NO_DEFAULT_CONTENT_META property or similar. 3. Other ideas?
--- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/719#issuecomment-90239600
