From 1fdc96a3817e802209b0ffe580ff6f12c7335551 Mon Sep 17 00:00:00 2001 From: Maxime Beauchemin Date: Mon, 20 May 2019 16:58:36 -0700 Subject: [PATCH] Disabling flask-talisman by default (#7535) flask-talisman was enabled recently and while it may be virtuous in some cases, it seems to break things out of the box. Locally and in dev mode, upon my first redirect it sends to HTTPS and things it crashes. I think it should be opt-in, maybe we can recommend turning this on in production in the docs? --- superset/config.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/superset/config.py b/superset/config.py index 4949bf903b45f..5f9bd8a3bf2f9 100644 --- a/superset/config.py +++ b/superset/config.py @@ -613,7 +613,7 @@ class CeleryConfig(object): } # Do you want Talisman enabled? -TALISMAN_ENABLED = True +TALISMAN_ENABLED = False # If you want Talisman, how do you want it configured?? TALISMAN_CONFIG = { 'content_security_policy': None,