Separating header information
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Hi
Love raptor-rpc.
Quick question ...
Is it possible to send a request like the following where the header information is separate
curl --location --request POST 'http://xxx.xxxs.xx.xx:8080' \
--header 'Content-Type: application/json' \
--header 'jsonrpc: 2.0' \
--header 'method: my_raptor_method' \
--header 'id: 1' \
--data-raw '{"params":[{"function_name": "add", "arguments": [1, 2]}]}'
The goal being to separate the business logic params; making them part of the body (leaving the system related reusable metadata in the header)
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
No source files or tests are identified in the issue. Start by tracing how raptor-rpc parses the curl request and JSON-RPC fields, then determine whether the proposed header/body separation is supported or needs a defined API change; done means the request format and expected handling are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100