Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Limitations: pinpoint how to invalidate all active sessions #118

Merged
merged 1 commit into from
Apr 10, 2020
Merged

Limitations: pinpoint how to invalidate all active sessions #118

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/limitations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ never be shared with the client MUST be avoided.
This is actually also valid for traditional PHP sessions, since those
sessions may be read by various processes.

#### Sessions cannot be invalidated
#### Single sessions cannot be invalidated

There is no way to (securely) manually invalidate a session just via
PSR7Session Storageless.
Expand All @@ -35,6 +35,9 @@ This limitation is also why PSR7Session Storageless should only be used with sec
(TLS) HTTPS connections: if any session is spoofed, there is no way to lock
out an attacker.

Note however that you can still securely invalidate all active sessions by changing
the key.

#### Increased network traffic

This is a very minor detail, but you may have increased network transfer
Expand Down