We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There seems to be an inconsistency in the way that ETags are handled. Calls to GetObjectAsync and StatObjectAsync strip the double quotes -
GetObjectAsync
StatObjectAsync
ObjectStat.cs
case "etag": objInfo.ETag = paramValue.Replace("\"", string.Empty, StringComparison.OrdinalIgnoreCase); break;
while PutObjectAsync does not strip the quotes -
PutObjectAsync
PutObjectResponse.cs
if (parameter.Key.Equals("ETag", StringComparison.OrdinalIgnoreCase)) { Etag = parameter.Value; break; }
The format of an ETag should be consistent across the whole API.
Also, there is an inconsistency in the spelling. PutObjectResponse uses a lower case 't' in Etag, while ObjectStat uses an upper case 'T' in ETag.
PutObjectResponse
ObjectStat
The text was updated successfully, but these errors were encountered:
The refactoring task currently I am working on will also address this issue.
Sorry, something went wrong.
ebozduman
No branches or pull requests
There seems to be an inconsistency in the way that ETags are handled. Calls to
GetObjectAsync
andStatObjectAsync
strip the double quotes -ObjectStat.cs
while
PutObjectAsync
does not strip the quotes -PutObjectResponse.cs
The format of an ETag should be consistent across the whole API.
Also, there is an inconsistency in the spelling.
PutObjectResponse
uses a lower case 't' in Etag, whileObjectStat
uses an upper case 'T' in ETag.The text was updated successfully, but these errors were encountered: