On 09/01/2014 07:54 AM, Rich B wrote: > On Thursday, August 14, 2014 9:02:40 PM UTC-4, Nikolaus Rath wrote: > > On 08/14/2014 03:17 PM, Adam Watkins wrote: > > Upgrading from revision 20 to 21... > > Unexpected server reply to copy operation: > > 200 OK > > Date: Thu, 14 Aug 2014 21:04:15 +0000 > > Server: RestServer/1.0 > > Content-Length: 189 > > Content-Type: application/xml > > ETag: "d7ed6a310a47b69a91e13e655245fac9" > > Cache-Control: no-cache > > Connection: close > > > > <?xml version="1.0" encoding="UTF-8"?> > > > <CopyObjectResult><LastModified>2014-08-14T21:04:15.000Z</LastModified> > > <ETag>"d7ed6a310a47b69a91e13e655245fac9"</ETag> > > </CopyObjectResult> > > > > [...] > > > Does this look like a deviation from S3-compatibility, which I should > > report to GreenQloud? > > Yes. They are not declaring the proper XML namespace (which would be > http://s3.amazonaws.com/doc/2006-03-01/ > > <http://www.google.com/url?q=http%3A%2F%2Fs3.amazonaws.com%2Fdoc%2F2006-03-01%2F&sa=D&sntz=1&usg=AFQjCNHS3kxugwRdqhZ6oS1Bzav7PPtrmQ>) > for the CopyObjectResult tag. > > Best, > -Nikolaus > > > Sorry to re-open an old thread, But I've run into a similar problem with > Dream Host's "S3 Compatible" DreamObjects. When I create a filesystem, > touch a file, and then umount it I get the following: > [...] > Backing up old metadata... > Unexpected server reply: expected XML, got: > 200 OK > Date: Mon, 01 Sep 2014 14:45:08 +0000 > Server: Apache > Transfer-Encoding: chunked > Content-Type: binary/octet-stream > > > Is this the same problem?
Almost. The Dreamhost response is different from the GreenQloud response, but they're both not S3-like. > If so, I'd like to report the bug to Dream Host, but the link Nikolaus > provided above does not work, so I don't know how to describe the bug to > them. That wasn't a link, "http://s3.amazonaws.com/doc/2006-03-01/"; is the XML namespace (which happens to look like an URL), that was not correctly declared by GreenQloud. > Could some one provide a link to (of description of) the S3 API call > that I piont to when submitting a bug report to D H? Here's an example for a proper response: 200 OK Date: Mon, 01 Sep 2014 14:45:08 +0000 Server: Apache Transfer-Encoding: chunked Content-Type: text/xml; charset=utf-8 <?xml version="1.0" encoding="UTF-8"?> <CopyObjectResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/";> <LastModified>2009-10-28T22:32:00</LastModified> <ETag>"9b2cf535f27731c974343645a3985328"</ETag> </CopyObjectResult> Note the difference in Content-Type, and the presence of a proper response body. You can find more information at This from http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectCOPY.html, but note that the examples at the end are actually incomplete (or outdated) and do not correspond to what S3 is actually returning. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to s3ql+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
