-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
question: custom method support #3482
Comments
Why do people want to use HTTP but without following normal HTTP conventions? What is the use case? |
To use an app protocol over HTTP. The use case is RPC using methods for procedure names. RFC 2616 allow to extend basic methods with custom ones.
Why do you want to block this standard feature ? |
I'm not a Deno maintainer, but personally I don't implement something just because a standard allows for it. It's important to show a concrete use case that doesn't have a cleaner solution. I would be willing to implement this in Pogo if Deno supports it. |
The problem in node.js was that http parser was blocking the ability to use other methods that listed ones. It was deliberately blocked. The question here is "is the http parser rigidity same as nodejs" ? Your framework could not do it if deno block it. |
@ry thanks for answer |
On node it is not possible to use custom method even if RFC 2616 allow it. It was due to hard code allowed method list on http parser. see nodejs/node-v0.x-archive#3192
Does deno allow to use custom methods ?
The text was updated successfully, but these errors were encountered: