I filed feature request https://issues.apache.org/jira/browse/JCLOUDS-793
Yes, the ParseETagHeader class throws an exception, but this doesn't report what went wrong; it could be the blobstore is broken and omitted the etag! (yes, highly unlikely, but a precise response would be much more useful) thank you On Wed, Dec 10, 2014 at 11:33 AM, Ignasi Barrera <n...@apache.org> wrote: > I see what you say, Daniel. > > The returned value has changed. Old swift API was using the > ParseETagHeader class [1] to parse the response for the putObject > request, but the new one is using the ETagHeader class [2] for that > purpose. The former threw an exception if the etag wasn't present but > the latter just silently returns null. > > [snip] -- Daniel Hsueh -- mailto:daniel.hs...@seagate.com <daniel.hs...@seagate.com> tel:+1-905-287-2167
