308 Redirect Error When Creating a New Dashboard on Superset Deployed via AKS

[Shlok-177]

I recently started encountering a 308 redirect error when creating a new dashboard in Superset. The error occurs because the URL is being redirected incorrectly to htppss:// instead of https://.

Deployment Environment: AKS (Azure Kubernetes Service)
Superset Version: 4.0.1
Issue Details: This issue did not occur previously but has started recently. I suspect there may be a misconfiguration related to the reverse proxy or SSL settings.
Repro Steps:
1.Access the Superset UI.
2.Attempt to create a new dashboard.
3.Observe the 308 redirect and the malformed URL (htppss://).

What I’ve Tried:
1.Verified ingress and reverse proxy configuration.
2.Checked environment variables and Superset settings related to URL generation and SSL.

Questions:

1.Has anyone encountered a similar issue with incorrect redirection to htppss://?
2.Are there specific configurations in Superset or ingress settings that might cause this behavior?
3.What can I do to debug or resolve this issue?

[dosubot[bot]]

Hey @Shlok-177! I'm here to help you with your Superset issue. I can assist with debugging and resolving the problem while you wait for a human maintainer. Let's get to the bottom of this!

I found a similar unsolved discussion titled "308 http error when creating new dashboard" which might be related to the issue you're experiencing ^[1].

Regarding your questions:

1. Similar Issues: The issue of incorrect redirection to "htppss://" seems unique, but it could be related to misconfigurations in the reverse proxy or ingress settings.

2. Configurations Affecting Redirection: In Superset's ingress settings, configurations such as annotations, ingress class name, TLS settings, and path configurations can affect URL redirection. Ensure that the X-Forwarded-Proto header is correctly set to "https" in your reverse proxy configuration. This is crucial for Superset to correctly interpret the original request protocol ^[2][3].

3. Debugging and Resolution:

   • Verify that the reverse proxy or ingress controller is correctly setting the X-Forwarded-Proto header.
   • Check if ENABLE_PROXY_FIX is set to True in your superset_config.py to ensure Superset uses the forwarded headers properly ^[2].
   • Review your ingress and reverse proxy configurations for any typos or incorrect settings that might lead to malformed URLs.

These steps should help you identify and resolve the redirection issue.

To continue talking to Dosu, mention @dosu.

[Shlok-177]

I solved that issue in AKS i configure nginx configuration : - i mistakely add below configuration in that file

`
nginx.ingress.kubernetes.io/proxy-redirect-from: http

nginx.ingress.kubernetes.io/proxy-redirect-to: https

nginx.ingress.kubernetes.io/force-ssl-redirect: 'true'

`
so i just removed first two line and go with only

nginx.ingress.kubernetes.io/force-ssl-redirect: 'true'
and error is solved.