No description
Find a file
Ferdinand Kuhl c09d5e0d1b
All checks were successful
ci/woodpecker/push/code-style Pipeline was successful
ci/woodpecker/push/functional-tests Pipeline was successful
Merge tag '4.0.0' into develop
Tagging 4.0.0
2023-01-10 12:03:39 +01:00
.woodpecker - try to fix CI trouble without error message 2023-01-10 11:59:18 +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 - Allow PHP 7.4 again, as no PHP 8.1 features are necessary to work 2023-01-10 12:00:53 +01: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())"