Databases
StackOverflow2013
Postsdbo
POExpress/Connect: Unable to parse body after making call to redis
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POExpress/Connect: Unable to parse body after making call to redis
    primarykey
    data
    text
    <p>I am trying to shorten my Express/Connect middleware pipeline by only calling certain middleware functions based on the requested path.</p> <p>However, the following will fail:</p> <pre><code>_cookieParser(req, res, function(err) { if(err) return next(err); _session(req, res, function(err) { if(err) return next(err); _csrf(req, res, function(err) { if(err) return next(err); loadUserFromSession(req, res, function(err) { if(err) return next(err); if(req.method == "POST") { _bodyParser(req, res, next); } else { next(); } }); }); }); }); </code></pre> <p>But this will work fine:</p> <pre><code>_cookieParser(req, res, function(err) { if(err) return next(err); _session(req, res, function(err) { if(err) return next(err); _csrf(req, res, function(err) { if(err) return next(err); _bodyParser(req, res, function(err) { if(err) return next(err); loadUserFromSession(req, res, next); }); }); }); }); </code></pre> <p>Where loadUserFromSession is:</p> <pre><code>function loadUserFromSession(req, res, next) { if(req.session &amp;&amp; req.session.userId) { userFunctions.getUserById(req.session.userId, function(err, user) { if(err) return next(err); if(user) { req.user = user; return next(); } else { req.session.destroy(); return next(new Error('Unauthenticated')); } }); } else { return next(new Error('Unauthenticated')); } }; </code></pre> <p>Why can I not call bodyParser() after loadUserFromSession()?</p> <p><strong>EDIT</strong></p> <p>Sorry for the lack of detail on the failure/unexpected outcome.</p> <p>If I put bodyParser() or just json() (since the POST content is json) after loadUserFromSession(), the calls never return inside of json(). If I put breakpoints in node inspector on either res.on('data') or res.on('end') neither get tripped.</p> <p>The source of the json middleware is below:</p> <pre><code>exports = module.exports = function(options){ var options = options || {} , strict = options.strict !== false; var limit = options.limit ? _limit(options.limit) : noop; return function json(req, res, next) { if (req._body) return next(); req.body = req.body || {}; if (!utils.hasBody(req)) return next(); // check Content-Type if ('application/json' != utils.mime(req)) return next(); // flag as parsed req._body = true; // parse limit(req, res, function(err){ if (err) return next(err); var buf = ''; req.setEncoding('utf8'); req.on('data', function(chunk){ buf += chunk &lt;==BREAKPOINT NEVER GETS CALLED }); req.on('end', function(){ var first = buf.trim()[0]; &lt;==BREAKPOINT NEVER GETS CALLED if (0 == buf.length) { return next(400, 'invalid json, empty body'); } if (strict &amp;&amp; '{' != first &amp;&amp; '[' != first) return next(400, 'invalid json'); try { req.body = JSON.parse(buf, options.reviver); next(); } catch (err){ err.body = buf; err.status = 400; next(err); } }); }); } }; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDave
    1. USDave
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COPlease edit your question and replace "will fail" with the actual error message and stack trace or describe the misbehavior if the failure isn't an error.
      singulars
      1. POExpress/Connect: Unable to parse body after making call to redis
      1. USPeter Lyons
    2. COSide comment, there are less nesty ways to use middleware. What you have above is unidiomatic for express (to put it politely). Try `app.use('/some/path', someMiddleware)` if you only want to use some things in some paths, but really most middleware has infinitesimally small cost when it does not apply to the current request. For example, the bodyParser simply checks the request method and calls `next()` immediately if there is no body. It's a non-problem that you shouldn't try to solve.
      singulars
      1. POExpress/Connect: Unable to parse body after making call to redis
      1. USPeter Lyons
    3. CO@PeterLyons added more details on my problem. On the structure, I don't disagree with you at all. I'm down this path, not because of performance, but security. I didn't want my app uploading every file that could get POSTed. I've got some endpoints that are public, and some that are not. I don't want to have my app overloaded (or DDOS'd if it ever became known) just by people uploading files to endpoints that shouldn't allow uploads.
      singulars
      1. POExpress/Connect: Unable to parse body after making call to redis
      1. USDave
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload