Is there some way to make this change so that it's only applied when speaking to a Swift endpoint that actually exhibits this problem? Is this something that Swift is likely to fix soon?
--- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/97#issuecomment-42979224
