nuts-foundation / nuts-foundation/nuts-node
QoL: let ErrInvalidClientCall include request URL
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Currenly, it's logged as:
failed to retrieve remote OAuth Authorization Server metadata: invalid client call\nserver returned HTTP 404 (expected: 200)
It'd be nice if it were to specify the URL that was attempted.
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 ErrInvalidClientCall and the code that logs the remote OAuth Authorization Server metadata failure. Trace the request that returns HTTP 404 and determine how its URL is available at the error site. Done means the logged error includes the attempted request URL while retaining the existing status information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100