HTTP header names are case-insensitive

[drzraf]

I guess a Guzzle update or the swift provider HTTP server or a Swift update (or an intermediary proxy) changed the case of the HTTP headers and... getMetadata() started being empty what drove me crazy until I understood it.

[k0ka]

need a unit test for this case

[k0ka]

I'm also not sure we need this at all. It might break the backward compatibility as swift metadata would have double keys.

[drzraf]

It allows my $container->getMetadata()["temp-url-key"] code to work indistinctly on both OVH swift 2.33 (and its all-lowercase headers) but also on another provider's Swift 2.25 with mixed-case headers' names.

[drzraf]

need a unit test for this case

I'm sorry, I can't enter into such a thing.

[k0ka]

I merged case insensitive comparison. But filling the metadata must be the same for backward compatibility. I can release "uniform" metadata in the next major release, but I'm not planning it in the near future.

You might create an interface to check metadata case-insensitive. Like $object->hasMetadataKey($key), $object->getMetadataKey($key) instead of manually checking keys of $object->getMetadata() array. But this will also require tests.