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 was archived by the owner on Jan 21, 2020. It is now read-only.
It's not interpreting the request as a GET request; it's instead matching a query string argument (which can occur with ANY URI, not just those sent via GET).
I'm not sure why we check for the identifier in the query string arguments, to be honest; we likely shouldn't. However, to change that at this time would break backwards compatibility.
Can you answer a couple questions for me, please, so we can better evaluate your concerns?
Why are you sending the identifier using a query string argument in the first place?
What problems are you observing due to the current behavior, exactly?
This repository has been closed and moved to laminas-api-tools/api-tools-mvc-auth; a new issue has been opened at laminas-api-tools/api-tools-mvc-auth#1.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
zf-mvc-auth/src/Authorization/DefaultResourceResolverListener.php
Line 126 in 25dca76
This method can not identifier request type for authorization check.
I have REST service
Allowed methods is
COLLECTION -> GET
ENTIITY-> PUT
for authorization I have this configs
but when I'm sending request like this
zf auth think that this is ENTITY-> GET.
because of on line 137 you are checking also if identifier exist in query parameters
The text was updated successfully, but these errors were encountered: