Skip to content
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

Non-Node.js HTTP adapter does not emit 'end' for http.ClientRequest #135

Open
whitlockjc opened this issue Oct 29, 2015 · 0 comments
Open

Comments

@whitlockjc
Copy link
Member

A user recently reported that req.on('end', function () { would not be ran when using Trireme and a non-Node.js HTTP adapter like the Netty one that is a part of this project. Here is the original report:

https://community.apigee.com/questions/12183/usage-of-middleware-after-response-sent.html

That thread also has a workaround but it would be nice if Trireme's non-Node.js HTTP adapters worked like Node.js itself does in this respect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant