Added the test. Recalled that the bug only manifests when copying a blob with changed metadata. You could lowercase the user metadata keys in copy options but still the fix will do the right thing which is sort headers lowercase as will Azure do when it will receive an uppercase header
-- 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/1185#issuecomment-371292328
