You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Are custom http verbs supported by io.js yet? #1081
Thus far, unless I missed it, I do not believe so. It's on my todo list to circle back on this but haven't had the opportunity (to be clear, I want to incorporate this into httpparser so that it'll be supported by both node and io.js)
Don't believe it did. I've since removed that particular branch because I fell out of date rather quickly. An updated fix would be quite similar tho. It's not too difficult to do just haven't had the opportunity to actually work on it.
PROPFIND or any other verb is supported just fine for outbound requests in node and iojs. There is either something else wrong with your request (wrong/bad headers or payload for example) or configuration on the server.
By the way, PROPFIND (and the other custom WebDAV methods) is supported by the HTTP parser at least since node v0.8. Outbound requests are not limited to a particular set of HTTP verbs.
Not yet. Once the new pure js http impl lands they should be, but for now,
the http-parser based impl supports only a fixed set of http verbs.
On May 26, 2015 7:03 AM, "Vladislav Botvin" notifications@github.com
wrote:
Custom HTTP verbs not working on iojs 2.1.0
Custom HTTP verb means any string what I want
—
Reply to this email directly or view it on GitHub #1081 (comment).
Activity
[-]Is custom http verbs supported by io.js yet?[/-][+]Are custom http verbs supported by io.js yet?[/+]jasnell commentedon Mar 6, 2015
Thus far, unless I missed it, I do not believe so. It's on my todo list to circle back on this but haven't had the opportunity (to be clear, I want to incorporate this into httpparser so that it'll be supported by both node and io.js)
Fishrock123 commentedon Mar 6, 2015
Requires a version of nodejs/http-parser#158 according to that issue. Not sure if a new patch ever landed.
jasnell commentedon Mar 6, 2015
Don't believe it did. I've since removed that particular branch because I fell out of date rather quickly. An updated fix would be quite similar tho. It's not too difficult to do just haven't had the opportunity to actually work on it.
mscdex commentedon Mar 6, 2015
Duplicated my SO answer here:
PROPFIND or any other verb is supported just fine for outbound requests in node and iojs. There is either something else wrong with your request (wrong/bad headers or payload for example) or configuration on the server.
Example of PROPFIND working:
mscdex commentedon Mar 6, 2015
By the way, PROPFIND (and the other custom WebDAV methods) is supported by the HTTP parser at least since node v0.8. Outbound requests are not limited to a particular set of HTTP verbs.
cjihrig commentedon Mar 6, 2015
Verified that this works in io.js.
darky commentedon May 26, 2015
Custom HTTP verbs not working on iojs 2.1.0
Custom HTTP verb means any string what I want
jasnell commentedon May 26, 2015
Not yet. Once the new pure js http impl lands they should be, but for now,
the http-parser based impl supports only a fixed set of http verbs.
On May 26, 2015 7:03 AM, "Vladislav Botvin" notifications@github.com
wrote:
darky commentedon May 26, 2015
So need reopen and close, when will released version of iojs with new pure js http
jasnell commentedon Mar 24, 2017
Closing. This is unlikely to happen at all with the http/1 implementation. The http/2 implementation will support any http verbs