- πΊπΈUnited States smustgrave
Reading #14 seems like this will be a much needed and welcomes test. Maybe #testing channel could help point where it should go. Or could CsrfTokenGeneratorTest be extended to cover this?
RouteProcessorCsrf::processOutbound()
does not take into account optional parameters when calculating a CSRF token, leading on-request validation to fail on a generated route in which one or more parameters were not provided at the time of generation.
Needs work
11.0 π₯
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Reading #14 seems like this will be a much needed and welcomes test. Maybe #testing channel could help point where it should go. Or could CsrfTokenGeneratorTest be extended to cover this?