No description
Find a file
Robin Krahnen 5d157194ee
All checks were successful
ci/woodpecker/push/code-style Pipeline was successful
ci/woodpecker/push/functional-tests/1 Pipeline was successful
ci/woodpecker/push/functional-tests/2 Pipeline was successful
ci/woodpecker/push/functional-tests/3 Pipeline was successful
update structure of composer.json and update dependencies
2024-10-15 08:55:20 +02:00
.woodpecker trying to understand matrix building 2023-01-26 13:02:02 +01:00
Classes Allow PHP 8.1 2023-01-10 11:55:58 +01:00
Configuration [WIP] migrates SessionLockRequestComponent to new MiddlewareInterface 2022-05-19 11:53:26 +02:00
Tests/Functional Allow PHP 8.1 2023-01-10 11:55:58 +01:00
composer.json update structure of composer.json and update dependencies 2024-10-15 08:55:20 +02:00
README.md Adding build status to README.md 2022-08-30 14:46:03 +02:00

DigiComp.FlowSessionLock

Build status

By default, the session established by Flow is not "protected" in any way. This package restricts every request to load the session only, if there are no other requests having it in access currently. It allows to set custom pointcut which will set the session in "ReadOnly" mode, which allows concurrent requests to read, but disallows the current request to write the session.

If you want to allow concurrent access somewhere, you can add your trigger pointcut in Settings.yaml like such:

DigiComp:
  FlowSessionLock:
    readOnlyExpressions:
      MyLock: "method(My\\Package\\Controller\\MyController->myAction())"