Handle all incoming and outgoing ETags according to RFC2616 / RFC7232
Fixes ETag handling in GetObject, HeadObject, CopyObject, UploadPartCopy APIs. We are now generating and storing ETags in the "RFC-Format" with enclosing double quotes. Incoming ETags are used verbatim to compare against the internally held representation. Wildcard ETags are also correctly handled. Fixes #807
Loading
Please sign in to comment