You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 4, 2018. It is now read-only.
I've found out that in the Symfony Security component you can restrict the firewall to be triggered upon a specific request (documentation).
In my case, for a certain endpoint of my API, I'd like the firewall to be triggered on a POST request but not on a GET request. Based on the documentation above I was planning to use something like the following when defining my security rules for Silex in a yaml file:
…re than just the URL (fabpot)
This PR was merged into the 1.3 branch.
Discussion
----------
updated the docs to show how to restrict a firewall by more than just the URL
closes#1171 and #1044
Commits
-------
721043c updated the docs to show how to restrict a firewall by more than just the URL
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've found out that in the Symfony Security component you can restrict the firewall to be triggered upon a specific request (documentation).
In my case, for a certain endpoint of my API, I'd like the firewall to be triggered on a POST request but not on a GET request. Based on the documentation above I was planning to use something like the following when defining my security rules for Silex in a yaml file:
But, checking on how the SecurityServiceProvider will handle that config, I've realized that the
methods
entry will be ignored:methods
key (code)Is this done for a particular reason or it's an oversight in Silex?
Could this behaviour be achieved in some other way?
The text was updated successfully, but these errors were encountered: