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

Issue #87: Do not call 'next()' after writing message body. #125

Merged
merged 1 commit into from Mar 19, 2018

Conversation

Projects
None yet
3 participants
@jwalton
Contributor

jwalton commented Mar 15, 2018

Fixes #87.

Issue #87: Do not call 'next()' after writing message body, as this w…
…ill likely cause other express handlers to attempt to write to the response after we've already written a response.
@coveralls

This comment has been minimized.

coveralls commented Mar 15, 2018

Coverage Status

Coverage decreased (-0.007%) to 95.761% when pulling 53c509b on jwalton:master into 4f3776b on theganyo:master.

2 similar comments
@coveralls

This comment has been minimized.

coveralls commented Mar 15, 2018

Coverage Status

Coverage decreased (-0.007%) to 95.761% when pulling 53c509b on jwalton:master into 4f3776b on theganyo:master.

@coveralls

This comment has been minimized.

coveralls commented Mar 15, 2018

Coverage Status

Coverage decreased (-0.007%) to 95.761% when pulling 53c509b on jwalton:master into 4f3776b on theganyo:master.

@theganyo theganyo merged commit 3f5c099 into apigee-127:master Mar 19, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment