Merged to master as
[17cef565](http://git-wip-us.apache.org/repos/asf/jclouds/commit/17cef565).
Thanks, @yuvalk!
@gaul given this slightly changes the behavior, should we cherry-pick it to
2.0.x?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
Closed #1164.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1164#event-1376378897
https://issues.apache.org/jira/browse/JCLOUDS-1363
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1164#issuecomment-348158562
Thanks, @yuvalk! Could you file an issue in our
[JIRA](https://issues.apache.org/jira/projects/JCLOUDS) so we can properly
track this?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/
Thanks for the info.
>
> On Nov 30, 2017 at 2:27 AM, mailto:notificati...@github.com)>
> wrote:
>
>
>
>
> HTTP headers are case insensitive by nature (see RFC 2616). When
> addUserMetadataTo check if this is indeed a user metadata header, it mu
HTTP headers are case insensitive by nature (see RFC 2616). When
addUserMetadataTo check if this is indeed a user metadata header, it must
properly ignore case.
The fix make sure that both metadataPrefix and the header key are compared with
toLowerCase().
This solves issue with minio metadata r
