axhza opened a new issue #11431: URL: https://github.com/apache/incubator-superset/issues/11431
Superset 0.37.2 no longer works behind a load balancer. ### Expected results I expect load balancing functionality to work. ### Actual results 0.37.0: I had to disable CSRF protection to get superset to _barely_ work behind a load balancer. 0.37.2: It no longer works behind a load balancer at all. #### Screenshots The below screenshot is the web dev log when trying to access from the load balancer:  #### How to reproduce the bug To confirm this is the case, I fresh installed 0.37.2 from pip; I then went to the page behind the load balancer to see pic above. ### Environment (please complete the following information): - superset version: `0.37.2` - python version: `3.6.9` - node.js version: NA - npm version: NA ### Checklist Make sure these boxes are checked before submitting your issue - thank you! - [X] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [X] I have reproduced the issue with at least the latest released version of superset. - [X] I have checked the issue tracker for the same issue and I haven't found one similar. ### Additional context The load balancer is an F5. Superset is serving directly using gunicorn (it's not proxied behind nginx). The gunicorn version is `20.0.4`. There are no stack traces in gunicorn. Everything works as normal when accessing directly (not through LB). Gunicorn config: ``` bind = "0.0.0.0:8080" workers = 2 max_requests = 5000 timeout = 120 keepalive = 30 limit_request_line = 0 limit_request_field_size = 0 forwarded_allow_ips = "x.x.x.x" secure_scheme_headers = {'X-Forwarded-For': 'https'} ``` Superset config: ``` ROW_LIMIT = 5000 # Flask-WTF flag for CSRF WTF_CSRF_ENABLED = False WTF_CSRF_EXEMPT_LIST = [] WTF_CSRF_TIME_LIMIT = 60 * 60 * 24 # Proxying ENABLE_PROXY_FIX = True SESSION_COOKIE_SAMESITE = None SESSION_COOKIE_HTTPONLY = False ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
