Skip to content

Corrected event name #96

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 6, 2017
Merged

Corrected event name #96

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .../posts/2017/03/2017-03-03-building-the-new-phalcon-website-middleware-part-3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Middleware needs to be attached to specific events in our events manager. These

* `before`: This attaches the middleware to the event that fires before the handler has been executed.
* `after`: This attaches the middleware to the event that fires after the handler has been executed.
* `final`: This attaches the middleware to the event that fires after the response has been sent to the caller.
* `finish`: This attaches the middleware to the event that fires after the response has been sent to the caller.

You can attach as many middleware classes in each of these events. They will be processed in a sequential manner, i.e. the first one registered gets processed first, then the second one etc.

Expand Down