fsprojects / fsprojects/FsHttp
Secrets and Logging / Stringifying
Open
Nobody has claimed this yet.
enhancement
security
- Dominant language
- F#
- Stars
- 498
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
When transforming requests / responses to string, secrets (like values from Authorization headers, and maybe others) could be omitted or rendered with ****
- could be a configurable aspect (on/off)
- the headers to which that behaviour applies could also be configurable
See discussion here: https://github.com/fsprojects/FsHttp/issues/195
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 by reading the discussion in issue #195 and locating the request/response stringification entry points in FsHttp. Determine the expected treatment of Authorization and other headers, the configuration boundaries, and the tests needed to show that secret values are omitted or masked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100