Skip to content
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

Open
ekampp opened this issue Jul 9, 2015 · 4 comments
Open

Support for the HTTP TRACE verb #1060

ekampp opened this issue Jul 9, 2015 · 4 comments

Comments

@ekampp
Copy link
Contributor

ekampp commented Jul 9, 2015

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.

@dblock
Copy link
Member

dblock commented Jul 9, 2015

👍 would like to see this in Grape

@ekampp
Copy link
Contributor Author

ekampp commented Jul 9, 2015

I suppose doing something like this could work?

@dblock
Copy link
Member

dblock commented Mar 14, 2016

We replaced the router in #1276. Maybe we can do something about this now? /cc: @namusyaka

@namusyaka
Copy link
Contributor

Sure, we can do provide the TRACE verb. I'm going to implement the new verb if @ekampp is not interested in the feature now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants