-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for the HTTP TRACE verb #1060
Labels
Comments
👍 would like to see this in Grape |
I suppose doing something like this could work? |
Closed
ekampp
added a commit
to ekampp/grape
that referenced
this issue
Jul 15, 2015
We replaced the router in #1276. Maybe we can do something about this now? /cc: @namusyaka |
Sure, we can do provide the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: