Sails: Skipper: Error on uploading base64 image

[Eklado]

Hello,
I get the following error on uploading base64 image.

Unable to parse HTTP body- error occurred :: 'Error: EUNFNTEX: Timed out waiting for known text parameters to finish streaming their bytes into the server.\n at setTimer (/app/node_modules/skipper/lib/Parser/prototype.parseReq.js:177:23)\n at Timeout.<anonymous> (/app/node_modules/skipper/node_modules/async/lib/async.js:758:21)\n at Timeout._onTimeout (/app/node_modules/skipper/node_modules/async/lib/async.js:173:37)\n at tryOnTimeout (timers.js:224:11)\n at Timer.listOnTimeout (timers.js:198:5)'

I found only one solution for this issue:

http://www.howtobuildsoftware.com/index.php/how-do/bkPE/nodejs-base64-sailsjs-data-uri-data-url-sailsjs-upload-huge-base64-image

It's working on normal servers, BUT this solution not possible on Heroku, since I can't make changes in the node modules on the server (Heroku files is read only).
So did anyone found a better solution for this issue?
it is preferable to set the request timeout value in the config files.

Sails version: 0.12.4
Node.js version: 4.4.5
NPM version: 2.15.5
Test Server: Ubuntu
Live Server: Heroku

Thank you in advance

https://github.com/balderdashy/skipper/issues/112

[sailsbot]

@Eklado Thanks for posting, we'll take a look as soon as possible. In the meantime, if you haven’t already, please carefully read the issue contribution guidelines and double-check for any missing information above. In particular, please ensure that this issue is about a stability or performance bug with a documented feature; and make sure you’ve included detailed instructions on how to reproduce the bug from a clean install. Finally, don’t forget to include the version of Node.js you tested with, as well as your version of Sails or Waterline, and of any relevant standalone adapters/generators/hooks.

Thank you!

[mikermcneil]

@Eklado Would you mind posting the http request you're using? (I realize it'll be kind of big, sorry about that, just need to get a sense of what the request actually looks like). Thanks!

Side note: if you ever need to install a fork of a NPM package on heroku, the easiest solution is to change the name in your fork's package.json file to a namespaced version. E.g. if your npm username is eklado, then you would change the name to @eklado/skipper. Then commit that and run npm version patch. Then push it up to your fork on GitHub. Finally, run npm publish. Then you'll be able to run npm install @eklado/skipper --save in your Sails app. Hope that helps!

[Eklado]

@mikermcneil Thank you for your reply
I attached a sample of the request. Request.txt

[raqem]

Hi @Eklado,
Just wanted to let you know we are moving all open Sails issues into one repo to help keep a better eye on things.
~Cheers!

[raqem]

Hi @Eklado, We are further cleaning Sails issues by closing older issues.

[vaskaloidis]

So we have no solution to this yet?

[Salablefuzzball]

This is still an issue with slow connections.