wfe: remove old user-agent context key
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go, grpc
- Domain
- backend-api-design
Research direction
Start by reading issue #8723 and trace where the User-Agent is stored in the context for gRPC. Remove the old context key once the new key is in use, then verify that the remaining User-Agent handling still treats the value as binary data.
Written by the indexing model from the issue text.
Description
In #8723 we added a new context key when storing the User-Agent, to indicate to gRPC that it should be treated as binary data. Once that's deployed we should remove the old context key.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
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.
More from letsencrypt/boulder
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
letsencrypt/boulder#8979 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
letsencrypt/boulder#9022 ·
-
letsencrypt/boulder#9021 · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 39/100
letsencrypt/boulder#9020 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
letsencrypt/boulder#9018 ·
All issues in letsencrypt/boulder
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100