-
-
Notifications
You must be signed in to change notification settings - Fork 474
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
Missing request data events #6
Comments
This was actually implemented specifically so that Are you still running into this problem? |
I'm running into this problem as well I'm using this module for static/sync cors headers before proxying to a couchDB url but it still consumes my request. I can understand the pause() calls, but I have a harder time understanding why resume() is called. Anyway, this is not the recommended way of doing things in node >=0.10. pause() and resume() cause the request to switch to old streams mode and thus consuming the stream before I get a chance to use it. Most importantly, it causes this fix (nodejs/node-v0.x-archive#4969) to be unefficient. Since i'm using request to do one-line proxying, I have some lines like this down the middleware chain.
since I can see several fixes for this.
my fix for my own problem for now is to remove cors altogether and set my static header myself =) |
Let me look into this. |
I've removed |
Thanks!
|
Is there a reason for the request.pause() / resume() calls? Because (in node 0.10) request handlers now miss data events. Removing the pause/resume from the cors module resolves the problem.
Any thoughts on this?
The text was updated successfully, but these errors were encountered: