Skip to content
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.

Do not mark response as complete in FinalHandler #54

Merged
merged 2 commits into from
Mar 24, 2016

Conversation

weierophinney
Copy link
Member

As reported in #53, because utilities such as the SapiEmitter need to update the response prior to sending it, marking the response as complete has an adverse impact since the release of 1.2.0, as this will now cause an exception.

This patch fixes that situation by using the write() method in favor of end() within the FinalHandler::completeResponse() method.

As reported in zendframework#53, because utilities such as the `SapiEmitter` need to update
the response prior to sending it, marking the response as complete has an
adverse impact since the release of 1.2.0, as this will now cause an exception.

This patch fixes that situation by using the `write()` method in favor of
`end()` within the `FinalHandler::completeResponse()` method.
@weierophinney weierophinney added this to the 1.2.1 milestone Mar 24, 2016
@weierophinney weierophinney self-assigned this Mar 24, 2016
@weierophinney weierophinney merged commit 60493e2 into zendframework:master Mar 24, 2016
weierophinney added a commit that referenced this pull request Mar 24, 2016
weierophinney added a commit that referenced this pull request Mar 24, 2016
weierophinney added a commit that referenced this pull request Mar 24, 2016
@weierophinney weierophinney deleted the hotfix/53 branch March 24, 2016 22:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant