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.

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

docs: document guards behavior when placed at controller and app level #3230

Merged
merged 2 commits into from
Mar 22, 2024
Merged

docs: document guards behavior when placed at controller and app level #3230

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
db9e33c
docs: document guards behavior when placed at controller and app level
guacs Mar 20, 2024
82c36ae
Merge branch 'main' into document-guards-limitation
guacs Mar 22, 2024
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
6 changes: 6 additions & 0 deletions docs/usage/security/guards.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,12 @@ As you can see in the above examples - ``guards`` is a list. This means you can
Unlike ``dependencies`` , guards do not override each other but are rather *cumulative*. This means that you can define
guards on different levels of your app, and they will combine.

.. caution::

If guards are placed at the controller or the app level, they **will** be executed on all ``OPTIONS`` requests as well.
For more details, including a workaround, refer https://github.com/litestar-org/litestar/issues/2314.


The route handler "opt" key
---------------------------

Expand Down
Loading