Access-Control-Allow-Headers content-type, as in, it probably won't allow the
x-csrf-tokenheader. And indeed, if I make the request with that header present, I get "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:1337/recipe. (Reason: header ‘x-csrf-token’ is not allowed according to header ‘Access-Control-Allow-Headers’ from CORS preflight response)." Sup with that?
Hi everyone. Sails (1.2.3) with Node backend app issue.
I'm having issue below:
ERR error: 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 (/home/vcap/app/node_modules/sails/node_modules/skipper/lib/private/Parser/prototype.parseReq.js:182:23)\n at Timeout.<anonymous> (/home/vcap/app/node_modules/sails/node_modules/skipper/node_modules/async/dist/async.js:2959:48)\n at Timeout._onTimeout (/home/vcap/app/node_modules/sails/node_modules/skipper/node_modules/async/dist/async.js:339:31)\n at ontimeout (timers.js:498:11)\n at tryOnTimeout (timers.js:323:5)\n at Timer.listOnTimeout (timers.js:290:5)'
This happens with a feature from our front end that parses a CSV and sends that data in json to backend, but the request fails with the error above.
I've tried updating default timeout from 5ms to 5000ms in node_modules/skipper/lib/Parser/prototype.parseReq.js ~linw:160 function finally_waitForTextParams().
I've also tried setting an environment variable in my manifest file to increase max http header size with NODE_OPTIONS: --max_old_space_size=4096.
Both haven't helped.
Anyone encounter this before or have any recommendations for what to try?
Hi all, I am getting issues trying to start sails using
sails lift. I keep getting these error messages
error: error: Error: Sails is taking too long to load. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Troubleshooting tips: -• Were you still reading/responding to an interactive prompt? (Whoops, sorry! Please lift again and try to respond a bit more quickly.) -• Do you have a lot of stuff in `assets/`? Grunt might still be running. (Try increasing the hook timeout. Currently it is 40000. e.g. `sails lift --hookTimeout=80000`) -• Is `blueprints` a custom or 3rd party hook? (*If* `initialize()` is using a callback, make sure it's being called.) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- at Timeout.tooLong [as _onTimeout] (K:\PC\pods\node_modules\sails\lib\app\private\loadHooks.js:191:21) at listOnTimeout (internal/timers.js:551:17) at processTimers (internal/timers.js:494:7) error: Could not load Sails app. error: error: Tips: error: • First, take a look at the error message above. error: • Make sure you've installed dependencies with `npm install`. error: • Check that this app was built for a compatible version of Sails. error: • Have a question or need help? (http://sailsjs.com/support)
I have removed Grunt tasks from running, I also removed all custom hooks from running but I don't get why these errors still keep occurring. It normally happens when I set the migration method to
alter. If I keep it on
safe, the server starts up easily, but on
drop, I always have the issue. I am actually confused. Could it be that another hook might be running somewhere.?
I don't know about any
blueprints hook that might be running. I went through the
blueprints.js file and everything seems normal there, as its a single export with some properties.