Add ETag to header when operation is against single entity
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 505
- Forks
- 186
- PR merge metrics
- No merged PRs in 30d
Description
Before .Net Core, adding an ETag to the response header was possible using:
config.MessageHandlers.Add(new ETagMessageHandler());
Using .Net Core, how can I achieve the same: add an ETag to the header when an operation is against a single entity?
Essentially I am looking for a way to enable concurrency checking using the .Net Core OData Library.
See link to OData repository for more info.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked RESTier ETag documentation and compare its ETagMessageHandler approach with the current ASP.NET Core OData library. Identify the supported path for enabling concurrency checking on single-entity operations; the work is complete when that path is implemented or documented and verified for ETag response headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100