request entity too large

[BenjaminHorn]

If I try to send a json to the server, which is about 220kb. (It contains a base64 coded image as a long string). I am getting the following error:

{"errors":[{"status":413,"source":"","title":"Error","code":"","detail":"request entity too large"}]}

server/confing.json

{
  "restApiRoot": "/api",
  "host": "0.0.0.0",
  "port": 3001,
  "remoting": {
    "context": {
      "enableHttpContext": false
    },
    "rest": {
      "normalizeHttpPath": false,
      "xml": false
    },
    "json": {
      "strict": false,
      "limit": "50mb"
    },
    "urlencoded": {
      "extended": true,
      "limit": "50mb"
    },
    "cors": false,
    "errorHandler": {
      "disableStackTrace": false
    }
  },
  "legacyExplorer": false
}

[raymondfeng]

Do you have a json parser set up in the middleware.json or server.js?

Thanks,

---

Raymond Feng (rfeng@us.ibm.com)
Co-Founder and Architect @ StrongLoop, Inc. (An IBM Company)

StrongLoop http://strongloop.com/ makes it easy to develop APIs http://strongloop.com/mobile-application-development/loopback/ in Node, plus get DevOps capabilities http://strongloop.com/node-js-performance/strongops/ like monitoring, debugging and clustering.

On Dec 3, 2015, at 10:29 AM, BenjaminHorn notifications@github.com wrote:

If I try to send a json to the server, which is about 220kb. (It contains a base64 coded image as a long string). I am getting the following error:

{"errors":[{"status":413,"source":"","title":"Error","code":"","detail":"request entity too large"}]}

server/confing.json

{
"restApiRoot": "/api",
"host": "0.0.0.0",
"port": 3001,
"remoting": {
"context": {
"enableHttpContext": false
},
"rest": {
"normalizeHttpPath": false,
"xml": false
},
"json": {
"strict": false,
"limit": "50mb"
},
"urlencoded": {
"extended": true,
"limit": "50mb"
},
"cors": false,
"errorHandler": {
"disableStackTrace": false
}
},
"legacyExplorer": false
}
—
Reply to this email directly or view it on GitHub #1856.

[BenjaminHorn]

I did not alter any of those files. They look like this:

server.js

var loopback = require('loopback');
var boot = require('loopback-boot');

var app = module.exports = loopback();

app.start = function() {
  // start the web server
  return app.listen(function() {
    app.emit('started');
    var baseUrl = app.get('url').replace(/\/$/, '');
    console.log('Web server listening at: %s', baseUrl);
    if (app.get('loopback-component-explorer')) {
      var explorerPath = app.get('loopback-component-explorer').mountPath;
      console.log('Browse your REST API at %s%s', baseUrl, explorerPath);
    }
  });
};

// Bootstrap the application, configure models, datasources and middleware.
// Sub-apps like REST API are mounted via boot scripts.
boot(app, __dirname, function(err) {
  if (err) throw err;

  // start the server if `$ node server.js`
  if (require.main === module)
    app.start();
});

middleware.json

{
  "initial:before": {
    "loopback#favicon": {}
  },
  "initial": {
    "compression": {},
    "cors": {
      "params": {
        "origin": true,
        "credentials": true,
        "maxAge": 86400
      }
    }
  },
  "session": {},
  "auth": {},
  "parse": {},
  "routes": {
    "loopback#rest": {
      "paths": [
        "${restApiRoot}"
      ]
    }
  },
  "files": {},
  "final": {
    "loopback#urlNotFound": {}
  },
  "final:after": {
    "loopback#errorHandler": {}
  }
}

[BenjaminHorn]

@raymondfeng is there any news on this?

[richardpringle]

Hey @BenjaminHorn , do you have an sample repo from which I can reproduce the issue?
You can follow this guide which basically says to fork the loopback-sandbox and reproduce your issue in the fork, but any sample repo will do.

If I am not mistaken, you should be able to use a Node.js buffer object to transfer binary data instead of a string. I don't know your particular use case though.

[BenjaminHorn]

@richardpringle @raymondfeng After some investigation I found that the problem is the content type.
If I try to Post with

Content-Type:application/x-www-form-urlencoded; charset=UTF-8

then it works. My client (ember) app sends

contentType: 'application/vnd.api+json'

then the new limit has no effect.

Setting the type wont fix it. I know that is not in the strongloop documentation, only in https://www.npmjs.com/package/body-parser#type-2
server/config.json

...
  "remoting": {
    "context": {
      "enableHttpContext": false
    },
    "rest": {
      "normalizeHttpPath": false,
      "xml": false
    },
    "json": {
      "strict": false,
      "limit": "50mb"
      "type": "application/vnd.api+json"
    },
...

[digitalsadhu]

I believe this is an issue with loopback-component-jsonapi. Needs a quick fix.
https://github.com/digitalsadhu/loopback-component-jsonapi/blob/master/lib/headers.js#L33
Needs to not overwrite but rather merge with options defined elsewhere (link in config.json)
Does that sound like its the issue @BenjaminHorn ?

[BenjaminHorn]

thanks @digitalsadhu that was the issue indeed. I made a PR.

[tborja]

What's the fix on this? I am running loopback on Bluemix. I am getting the Request too large error using swagger js client.

[roboflank]

Also running into the same error