Repository navigation
Feature/http query method - #365
Conversation
The merged regression test only asserted getRoutes() ordering and never exercised the dispatch path, where the fatal BadRouteException was actually thrown. It also used non-conflicting static paths, so it could not reproduce the shadowing. Add a match-level test registering a named static route followed by an unnamed variable route, which fails with BadRouteException on the pre-fix code and passes on the fix. Also record the fix under a new Fixed section in the changelog (#362, #363).
QUERY (draft-ietf-httpbis-safe-method-w-body) is a safe, idempotent method like GET that permits a request body. Expose it as a standalone verb helper alongside the existing verbs; it delegates through map() like every other verb, so no dispatcher or allowlist change is needed.
Add the query verb to the Request Verbs sample and a CHANGELOG entry citing the IETF draft the method originates from.
|
That was pretty fast, I could have done it by myself😅
Thank you for your answer |
|
@zykogithub already released as part of 7.0.0 - https://github.com/thephpleague/route/releases this is a larger major release though so take a look at https://route.thephpleague.com/7.x/upgrade/ (if you need it in 6.x I'm happy for you to put a PR in for the 6.x branch that recreates it) as for your cdn question, I'm not sure without testing, it just accepts the method at the router level |
|
About cdn, I will try with production environment and we will see |
No description provided.