From 7d5c3a7a0f59642c5e9c99989376410155fe425b Mon Sep 17 00:00:00 2001 From: Yoshie Muranaka Date: Thu, 30 Jan 2020 14:38:29 -0800 Subject: Update config to keep 'secure' attribute Since switching to secure https protocol for development https://gerrit.openbmc-project.xyz/c/openbmc/webui-vue/+/28729/7 no need to remove 'secure' attribute from response header. Signed-off-by: Yoshie Muranaka Change-Id: Ic7bddb4572ec8ccd3029c493ca57627dd24b8ae4 --- vue.config.js | 8 -------- 1 file changed, 8 deletions(-) (limited to 'vue.config.js') diff --git a/vue.config.js b/vue.config.js index 429b273e..e40b01ef 100644 --- a/vue.config.js +++ b/vue.config.js @@ -19,14 +19,6 @@ module.exports = { // This header is igorned in the browser so removing // it so we don't see warnings in the browser console delete proxyRes.headers['strict-transport-security']; - if (proxyRes.headers['set-cookie']) { - // Need to remove 'Secure' flag on set-cookie value so browser - // can create cookie for local development - const cookies = proxyRes.headers['set-cookie'].map(cookie => - cookie.replace(/; secure/gi, '') - ); - proxyRes.headers['set-cookie'] = cookies; - } } } }, -- cgit v1.2.3