-
Notifications
You must be signed in to change notification settings - Fork 14
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.
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
Session storage is not binary safe #32
Comments
dnsl48
added a commit
to open-sausages/silverstripe-dynamodb
that referenced
this issue
Jun 27, 2019
… sessions as strings, which is not binary safe fixes silverstripe#32
dnsl48
added a commit
to open-sausages/silverstripe-dynamodb
that referenced
this issue
Jun 27, 2019
… sessions as strings, which is not binary safe fixes silverstripe#32
dnsl48
added a commit
to open-sausages/silverstripe-dynamodb
that referenced
this issue
Jul 1, 2019
dnsl48
added a commit
to open-sausages/silverstripe-dynamodb
that referenced
this issue
Jul 1, 2019
dnsl48
added a commit
to open-sausages/silverstripe-dynamodb
that referenced
this issue
Jul 1, 2019
dnsl48
added a commit
to open-sausages/silverstripe-dynamodb
that referenced
this issue
Jul 1, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
aws-sdk-php implementation of StandardSessionConnection is not binary safe. The issue reported here: aws/aws-sdk-php#1831
SilverStripe 4.4 core functionality persists some binary data within sessions (ConfirmationMiddleware CSRF), which makes this critical for SilverStripe Platform Multi-AZ, which utilizes DynamoDB as the session storage.
The text was updated successfully, but these errors were encountered: