Allow features to specify the criteria for considering a report successfully sent
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 84
- Forks
- 39
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 1
Description
Currently, the UA considers the report successfully sent if it receives a 2xx response code. However, some features might want to require other criteria to consider a report successfully sent: for example, retry until a 2xx response code is received over a connection using a CT-logged certificate.
It would be nice for the API to allow this somehow, even if just exposing the properties of the connection/response when a report is successfully sent so that the feature can re-enqueue a report if it wasn't sent to its satisfaction.
Contributor guide
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
No files or tests are named. Start by reviewing the Reporting API’s definition of a successfully sent report and the existing response and connection properties, then establish concrete acceptance criteria for feature-specific success checks and report re-enqueueing.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100