Support for the HTTP TRACE verb
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 10k
- Forks
- 1.2k
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 92
Description
Hi.
I thought I would start a discussion here, about how to approach implementing the HTTP TRACE verb.
This would be a great tool for developers integrating to an API in a test enviroinment. And also for developers developing new clients or APIs consuming a TRACEable API.
Since Grape already responds with HEAD and OPTIONS on all endpoints, I assume that we could find some way to implement the TRACE verb in a similar fashion?
All input is appreciated.
Thanks.
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 examining how Grape provides HEAD and OPTIONS on all endpoints, then compare the desired TRACE behavior with the linked HTTP specification. Done should mean that TRACE is supported consistently for the relevant endpoints, but the issue does not identify files, tests, or a precise scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100