Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
Http kernel controller arguments#10640
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
eb43c48 to36d3677Comparenicolas-grekas commentedNov 10, 2018
The |
ottaviano commentedNov 10, 2018
@nicolas-grekas, it seems that it was not enough as an explication2 years ago |
This PR was submitted for the master branch but it was squashed and merged into the 3.4 branch instead (closes#10640).Discussion----------Http kernel controller argumentsHi,I saw the issue#6854, and I can not write full & clear doc to describe the `kernel.controller_arguments` event.But I think that it will be nice to have this event in the list of all Kernel events.I fix the `kernel.finish_request` event description. This event is triggered after `kernel.response` event (not only for a sub-request).Commits-------cd5fe5a Http kernel controller arguments
javiereguiluz commentedApr 5, 2019
Thanks Dimitri! I'm really sorry it took us so long to merge this contribution ... but it's finally merged! |
Hi,
I saw the issue#6854, and I can not write full & clear doc to describe the
kernel.controller_argumentsevent.But I think that it will be nice to have this event in the list of all Kernel events.
I fix the
kernel.finish_requestevent description. This event is triggered afterkernel.responseevent (not only for a sub-request).