minio

Author	SHA1	Message	Date
Anis Elleuch	61927d228c	listV2: Continuation and NextContinuation tokens are encoded with base64 (#8337 ) Minio V2 listing uses object names/prefixes as continuation tokens. This is problematic when object names contain some characters that are forbidden in XML documents. This PR will use base64 encoded form of continuation and next continuation tokens to address that corner case.	2019-10-02 01:39:29 +05:30
Harshavardhana	e6d8e272ce	Use const slashSeparator instead of "/" everywhere (#8028 )	2019-08-06 12:08:58 -07:00
kannappanr	5ecac91a55	Replace Minio refs in docs with MinIO and links (#7494 )	2019-04-09 11:39:42 -07:00
Pontus Leitzler	b43e8337b1	Add error handling in api-resource.go (#6651 )	2018-10-18 07:31:46 -07:00
Praveen raj Mani	5fbdd70de9	Minio handle for list_objects_v2 with a blank ContinuationToken (#5940 ) minio will now return an error for a blank continuation token in list_objects_v2,so as in s3. Fixes #5931	2018-06-25 12:35:43 -07:00
Harshavardhana	adf9a9d300	Remove all unused variables and functions (#5823 )	2018-04-15 19:26:04 +05:30
Mateusz Gajewski	73982c8cb6	Listen bucket notification for multiple prefixes/suffixes (#2911 ) * Listen bucket notification for multiple prefixes/suffixes * After review fixes	2016-10-12 11:02:15 -07:00
Harshavardhana	ca3022d545	api: Change ListenBucketNotification with new API format. (#2791 ) Take prefix, suffix and events as query params.	2016-09-27 13:17:43 -07:00