[Content-Type] unsupported about node-restify HOT 3 CLOSED

So, short answer, no there's not currently a way to do this. That said, I can fix it in the next day or two.

Longer answer: 'accept' does work, but it drives "accept", not content-type for sending data. You're sending data in that custom type, not asking for it back in a custom type (if you did 'curl -is -H "Accept: application/x-chess-pgn" http://localhost:3020/pgn' restify wouldn't have choked). Currently it's hardcoded to parse out multipart/form-url/json.

What I've been meaning to do is to have you be able to specify a handler for each type, if you want it out of the way, and just ship defaults for the ones that are there. But that's a little bit of code refactoring - anyway, I'll knock that out soon.

from node-restify.

Ok, I put in support for this (see the commit above). Basically, if you want to "fully" support what you described above, do this:

var assert = require('assert');
var restify = require('restify');

 var server = restify.createServer({
   contentHandlers: {
     'application/x-chess-pgn': function(body) {
       assert.ok(body);

       return JSON.parse(body);
    }
  },
  contentWriters: {
    'application/x-chess-pgn': function(obj) {
      assert.ok(obj);

      return JSON.stringify(obj);
    }
  },
  accept: ['application/json', 'application/x-chess-pgn']
});

server.post('/pgn', function(req, res, next) {
  res.send(200, {success: true});
  return next();
});

server.listen(3020);

To pick this up, it's npm published as v0.3.8; I finally got around to reworking accept header handling, mostly because it choked on some simple tests I threw at it :).

Let me know if this works for you, and thanks for using restify!

m

from node-restify.

Hi Mark!
It's working now like a charm! Now I can parse files of different content-types. Thanks for your commit and support!

from node-restify.