Skip to content

Tidied up a bit of grammar and added a link to the EventDispatcher docs ... #1649

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
Aug 25, 2012
Merged

Tidied up a bit of grammar and added a link to the EventDispatcher docs ... #1649

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
10 changes: 5 additions & 5 deletions cookbook/event_dispatcher/before_after_filters.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,8 @@ or hooks.

In Symfony1, this was achieved with the preExecute and postExecute methods,
most major frameworks have similar methods but there is no such thing in Symfony2.
The good news is that there is a much better way to interfere the
Request -> Response process using the EventDispatcher component.
The good news is that there is a much better way to interfere with the
Request -> Response process using the :doc:`EventDispatcher component</components/event_dispatcher/introduction>`.

Token validation Example
------------------------
Expand All @@ -21,13 +21,13 @@ but some others are restricted to one or some clients. For these private feature
you might provide a token to your clients to identify themselves.

So, before executing your controller action, you need to check if the action
is restricted or not. And if it is restricted, you need to validate the provided
is restricted or not. If it is restricted, you need to validate the provided
token.

.. note::

Please note that for simplicity in the recipe, tokens will be defined
in config and neither database setup nor authentication provider via
Please note that for simplicity in this recipe, tokens will be defined
in config and neither database setup nor authentication via
the Security component will be used.

Creating a before filter with a controller.request event
Expand Down