-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot pipe request after body-parser #94
Comments
Hm, I'm not sure. I just made the following app and it works fine with a var bodyParser = require('body-parser')
var express = require('express')
var app = express()
.use(bodyParser.raw({ limit: '5mb' })
use(function (req, res) {
res.end('I saw ' + rew.body.length + ' bytes in the body')
})
express.listen(3000) It's very important that you do not have a |
With DEBUG set I get the following (incl. request headers).
The +33s is after several requests. After starting the node app there appear 0ms with the first request. The request I do with curl:
Reading from the request, writing to a file in this way:
Thanks for the quick reply! |
Ah, thanks, that |
With the answer it is so obvious. But I never had found it alone. |
My pleasure :) |
I'm using body-parser to limit the size of a POST body. Adding the following line a request with some 3MB stucks on '100 continue'. No data is written.
A request with 400kB is successful. Removing the above line the 3MB request (and larger requests) work fine.
I'm using version 1.12.3. Maybe I have overseen something!?
The text was updated successfully, but these errors were encountered: