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

Response emitter throws exception when warning or notice has been printed #17

Closed
mbunge opened this issue Oct 1, 2016 · 1 comment
Closed
Assignees

Comments

@mbunge
Copy link
Contributor

mbunge commented Oct 1, 2016

Add a flag which is disabling headers already send

@mbunge mbunge self-assigned this Oct 1, 2016
@mbunge
Copy link
Contributor Author

mbunge commented Oct 1, 2016

This happends in some specific calls and is not repeatable

mbunge pushed a commit that referenced this issue Oct 1, 2016
@mbunge mbunge closed this as completed in 499292e Oct 1, 2016
mbunge added a commit that referenced this issue Oct 4, 2016
* Add vagrant development environment

* Fix typo

* Fix #14 Delegate request content type to response

* Update changelog

* Fix #16 fix output buffer termination

add shutdown event
rename `Application::cleanUp` to `Application::collectGarbage`
rename `Application::finishRequest` to `Application::shutdown`

* Fix code style. Fluent setter update

* Fix #17 Add logic for forcing response emitting

* Fix #15 Enhance error handling logic

* update content delegation

* update loggers

* log errors on runtime errors

* fix typo

* fix typo

* Fix #3, #4, #5

* Update Application.php

* Fix wrong response determined by content type delegation

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

No branches or pull requests

1 participant