diff options
| author | Martin Geubelle <mge@odoo.com> | 2019-01-10 11:25:13 +0000 |
|---|---|---|
| committer | Martin Geubelle <mge@odoo.com> | 2019-02-13 09:38:30 +0000 |
| commit | 31664422c11ab1e9c34ad6b2eb1dfba2af72e359 (patch) | |
| tree | 15e14b87f3c99ae1fbe88a01aeeb54ff2884e1e3 /addons/web/static/src/js/core/session.js | |
| parent | 984bf2492a16f0ff357b3fc03712c68f1a011f96 (diff) | |
[IMP] web, *: remove explicit references to `session_id`
Since rev. odoo/odoo@f4d541e the `session_id` cookie uses the `httponly` flag so
it cannot be accessed through client side script. But before this rev. the
`session_id` was still provided by the server to the webclient (in session_info,
mostly) and was stored and accessible. This made XSS injection more
dangerous than they should be as it was very easy to steal the `session_id`.
As the browser automatically set the `session_id` on every request to the server,
the webclient shouldn't need any explicit reference.
Diffstat (limited to 'addons/web/static/src/js/core/session.js')
| -rw-r--r-- | addons/web/static/src/js/core/session.js | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/addons/web/static/src/js/core/session.js b/addons/web/static/src/js/core/session.js index 694285cccdc..968496c2a6d 100644 --- a/addons/web/static/src/js/core/session.js +++ b/addons/web/static/src/js/core/session.js @@ -139,7 +139,6 @@ var Session = core.Class.extend(mixins.EventDispatcherMixin, { if (!result.uid) { return $.Deferred().reject(); } - delete result.session_id; _.extend(self, result); }); }, @@ -290,7 +289,6 @@ var Session = core.Class.extend(mixins.EventDispatcherMixin, { */ session_reload: function () { var result = _.extend({}, window.odoo.session_info); - delete result.session_id; _.extend(this, result); return $.when(); }, |
