feat: Adding new CookieNameChange middleware (#28404)
Description: Adds a new middleware to help with cookie name changes. It uses the idea of expand and contract, where after we've changed the name, the middleware allows up to accept either a cookie with new name (given higher priority when both are present) or cookie with old name. This is also helpful when changing domain of a cookie. impacts: developers, users(anyone that has cookies) Change depends on django setting changes. See CookieNameChange middleware for more info.
Showing
- openedx/core/djangoapps/cookie_metadata/__init__.py 0 additions, 0 deletionsopenedx/core/djangoapps/cookie_metadata/__init__.py
- openedx/core/djangoapps/cookie_metadata/middleware.py 58 additions, 0 deletionsopenedx/core/djangoapps/cookie_metadata/middleware.py
- openedx/core/djangoapps/cookie_metadata/tests/__init__.py 0 additions, 0 deletionsopenedx/core/djangoapps/cookie_metadata/tests/__init__.py
- openedx/core/djangoapps/cookie_metadata/tests/test_cookie_name_change.py 109 additions, 0 deletions...angoapps/cookie_metadata/tests/test_cookie_name_change.py
Loading
Please register or sign in to comment