No description
Find a file
Robin Krahnen f55060ed3b
All checks were successful
ci/woodpecker/tag/code-style Pipeline was successful
ci/woodpecker/tag/functional-tests Pipeline was successful
ci/woodpecker/push/code-style Pipeline was successful
ci/woodpecker/push/functional-tests Pipeline was successful
Merge branch 'release/6.3.0'
2026-03-02 11:47:23 +01:00
.woodpecker replacing functional tests to now check only for PHP and Flow 8.4 2026-01-12 21:17:50 +01:00
Classes use http 429 in case of session lock 2026-03-02 11:44:54 +01:00
Configuration reduce wait time for acquiring lock 2026-03-02 11:46:40 +01:00
Tests/Functional Allow PHP 8.1 2023-01-10 11:55:58 +01:00
composer.json update symfony/lock 2026-02-10 12:36:10 +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())"