Skip to content

Commit 4e45170

Browse files
Add file and array to atomic lock cache driver list (#9139)
* Add file and array to atomic lock cache driver list * Update session.md --------- Co-authored-by: Taylor Otwell <taylor@laravel.com>
1 parent 34f1fac commit 4e45170

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

session.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -250,7 +250,7 @@ If you need to regenerate the session ID and remove all data from the session in
250250
## Session Blocking
251251

252252
> **Warning**
253-
> To utilize session blocking, your application must be using a cache driver that supports [atomic locks](/docs/{{version}}/cache#atomic-locks). Currently, those cache drivers include the `memcached`, `dynamodb`, `redis`, and `database` drivers. In addition, you may not use the `cookie` session driver.
253+
> To utilize session blocking, your application must be using a cache driver that supports [atomic locks](/docs/{{version}}/cache#atomic-locks). Currently, those cache drivers include the `memcached`, `dynamodb`, `redis`, `database`, `file`, and `array` drivers. In addition, you may not use the `cookie` session driver.
254254
255255
By default, Laravel allows requests using the same session to execute concurrently. So, for example, if you use a JavaScript HTTP library to make two HTTP requests to your application, they will both execute at the same time. For many applications, this is not a problem; however, session data loss can occur in a small subset of applications that make concurrent requests to two different application endpoints which both write data to the session.
256256

0 commit comments

Comments
 (0)