-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Added a short cookbook about avoiding the automatic start of the sessions #4661
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
Changes from 1 commit
99781f8
0212779
7dd3945
bbba47a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
…ions
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
.. index:: | ||
single: Sessions, cookies | ||
|
||
Avoid Starting Sessions for Anonymous Users | ||
=========================================== | ||
|
||
Sessions in Symfony applications are automatically started when they are necessary. | ||
This includes writing in the user's session, creating a flash message and logging | ||
in users. In order to start the session, Symfony creates a cookie which will be | ||
sent for every request. | ||
|
||
However, there are other scenarios when a session is started and therefore, a | ||
cookie will be created even for anonymous users. First, consider the following | ||
code commonly used to display flash messages: | ||
|
||
.. code-block:: html+jinja | ||
|
||
{% for flashMessage in app.session.flashbag.get('notice') %} | ||
<div class="flash-notice"> | ||
{{ flashMessage }} | ||
</div> | ||
{% endfor %} | ||
|
||
Even if the user is not logged in and even if you haven't created any flash message, | ||
just calling the ``get()`` method of the ``flashbag`` will start a session. This | ||
may hurt your application performance because all users will receive a session | ||
cookie. To avoid this behavior, add a check before trying to access the flash messages: | ||
|
||
.. code-block:: html+jinja | ||
|
||
{% if app.session.started %} | ||
{% for flashMessage in app.session.flashbag.get('notice') %} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok, so I don't think this is right - it's a confusing thing: A) B) There's a huge confusion over this - I was just reading symfony/symfony#6036 and symfony/symfony#6388 about this - the functionality for this is not right in the core, which is why this is so difficult. |
||
<div class="flash-notice"> | ||
{{ flashMessage }} | ||
</div> | ||
{% endfor %} | ||
{% endif %} | ||
|
||
Another scenario where session cookies will be automatically sent is when the | ||
requested URL is covered by a firewall, no matter if anonymous users can access | ||
to that URL: | ||
|
||
.. code-block:: yaml | ||
|
||
# app/config/security.yml | ||
security: | ||
firewalls: | ||
main: | ||
pattern: ^/ | ||
form_login: ~ | ||
anonymous: ~ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. xml and php are missing |
||
|
||
This behavior is caused because in Symfony applications, anonymous users are | ||
technically authenticated,. |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,4 +7,5 @@ Sessions | |
proxy_examples | ||
locale_sticky_session | ||
sessions_directory | ||
php_bridge | ||
php_bridge | ||
avoid_session_start |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.