Harshavardhana f108873c48 fix: replication metadata comparsion and other fixes (#11410) ... - using miniogo.ObjectInfo.UserMetadata is not correct - using UserTags from Map->String() can change order - ContentType comparison needs to be removed. - Compare both lowercase and uppercase key names. - do not silently error out constructing PutObjectOptions if tag parsing fails - avoid notification for empty object info, failed operations should rely on valid objInfo for notification in all situations - optimize copyObject implementation, also introduce a new replication event - clone ObjectInfo() before scheduling for replication - add additional headers for comparison - remove strings.EqualFold comparison avoid unexpected bugs - fix pool based proxying with multiple pools - compare only specific metadata Co-authored-by: Poorna Krishnamoorthy <poornas@users.noreply.github.com>		2021-02-03 20:41:33 -08:00
..
gateway-s3_test.go	Move dependency from minio-go v6 to v7 (#10042)	2020-07-14 09:38:05 -07:00
gateway-s3-metadata_test.go	use GlobalContext whenever possible (#9280)	2020-04-09 09:30:02 -07:00
gateway-s3-metadata.go	avoid double listObjectParts calls improves performance (#9606)	2020-05-15 08:06:45 -07:00
gateway-s3-sse.go	fix: replication metadata comparsion and other fixes (#11410)	2021-02-03 20:41:33 -08:00
gateway-s3-utils.go	add gateway object tagging support (#9124)	2020-05-23 11:09:35 -07:00
gateway-s3.go	tagging: Add event notif for PUT object tagging (#11366)	2021-02-01 13:52:51 -08:00