nspcc-dev / nspcc-dev/neofs-node
Node responds with `malformed request` status message clarification
Open
Nobody has claimed this yet.
enhancement
I3
neofs-storage
S3
U4
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Currently node can response with
status: code = 1024 message = malformed request
We have to underline the defect in the request, otherwise it will be extremely difficult for the client to identify the cause.
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
Start by locating the code that produces status code 1024 with the “malformed request” message, then trace the request validation path. The work is done when responses identify the defect in the request clearly enough for a client to determine its cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100