Are custom http verbs supported by io.js yet?

[unbornchikken]

According to this issue: nodejs/node-v0.x-archive#3192

Because I'm having this: http://stackoverflow.com/questions/28899036/node-js-cannot-do-profind-with-request-module

In a nushell I cannot do a PROPFIND request in node/io.js.

[jasnell]

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]

Requires a version of nodejs/http-parser#158 according to that issue. Not sure if a new patch ever landed.

[jasnell]

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]

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:

// client.js
require('http').request({
  host: '127.0.0.1',
  port: 8000,
  method: 'PROPFIND'
}, function(res) {
  res.resume();
}).end();

// server.js
require('http').createServer(function(req,res) {
  // echoes "PROPFIND" to stdout
  console.log(req.method);

  res.writeHead(200, { 'Connection': 'close' });
  res.end();
}).listen(8000);

[mscdex]

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]

Verified that this works in io.js.

[darky]

Custom HTTP verbs not working on iojs 2.1.0
Custom HTTP verb means any string what I want

[jasnell]

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).

[darky]

So need reopen and close, when will released version of iojs with new pure js http

[jasnell]

Closing. This is unlikely to happen at all with the http/1 implementation. The http/2 implementation will support any http verbs