Honor fetch-owner parameter during ListV2

In practice this emits bogus information.  Found via s3-tests.
pull/322/head
Andrew Gaul 2019-10-21 09:55:05 -07:00
rodzic b2c1d40bfd
commit f3f0913dc8
1 zmienionych plików z 5 dodań i 5 usunięć

Wyświetl plik

@ -1366,10 +1366,8 @@ public class S3ProxyHandler {
options.afterMarker(marker);
}
String fetchOwner = request.getParameter("fetch-owner");
if (fetchOwner != null && !fetchOwner.equals("false")) {
throw new S3Exception(S3ErrorCode.NOT_IMPLEMENTED);
}
boolean fetchOwner = !isListV2 ||
"true".equals(request.getParameter("fetch-owner"));
int maxKeys = 1000;
String maxKeysString = request.getParameter("max-keys");
@ -1497,7 +1495,9 @@ public class S3ProxyHandler {
writeSimpleElement(xml, "StorageClass",
StorageClass.fromTier(metadata.getTier()).toString());
writeOwnerStanza(xml);
if (fetchOwner) {
writeOwnerStanza(xml);
}
xml.writeEndElement();
}