Open PrasantJillella opened 1 year ago
@PrasantJillella Would you please share the Azurite debug log for this issue? For all kinds of table API that matters? We will need it to continue the investigation.
Hi
Sorry for delay, Updated the description with logs.
@PrasantJillella
Thanks for the update! The fix looks won't be too complex, might only need change the error kind when etag not match in related table request, from "getInvalidOperation" to "getInvalidInput". If you need the error message also be aligned besides error code, you might need to create a new kind of error.
Like in these line: Update Entity: https://github.com/Azure/Azurite/blob/800af6e9cd6639fa8a828c9b125c99f93707dc0e/src/table/handlers/TableHandler.ts#L397
Delete Entity:
Azurite welcome contribution! It would be great if you can raise a PR to fix it.
Which service(blob, file, queue, table) does this issue concern?
Table
Which version of the Azurite was used?
3.23.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
What's the Node.js version?
v18.14.2
What problem was encountered?
When sending malformed Etag for table operations like Update, Delete. It is noticed that Exception is thrown with ErrorCode: InvalidOperation. But the actual expected ErrorCode: InvalidInput.
Steps to reproduce the issue?
namespace for TableClient class is 'Azure.Data.Tables' Etag value sent= "MalformedETag" Below is sample code snippet to describe change involved.
If possible, please provide the debug log using the -d parameter, replacing \<pathtodebuglog> with an appropriate path for your OS, or review the instructions for docker containers:
Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.
Have you found a mitigation/solution?
No