sillsdev / sillsdev/languageforge-lexbox
location header is not redacted in logs
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
Describe the bug
When looking at the logs for lexbox the location header for redirects is shown, that value should be redacted in the logs as it may contain sensitive information.
Expected behavior
There's settings to control http response logging which includes what headers to log.
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 locating the HTTP response logging settings and the code that selects response headers for logging. Verify how redirect Location values are currently handled, then make the logging output redact or omit that header while preserving the existing configuration behavior. Done means sensitive Location values no longer appear in Lexbox logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, observability, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100