You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:19:49 UTC
Re: [D] If using a reverse proxy and finally accessing it with a domain name, some pages would report errors when accessed [superset]
GitHub user dosubot[bot] edited a comment on the discussion: If using a reverse proxy and finally accessing it with a domain name, some pages would report errors when accessed
<!-- Answer -->
To address the "400 Bad Request" error you're encountering when accessing Superset through a reverse proxy with a domain name, you can try the following solutions:
1. **Ensure Correct Header Configuration**: Make sure your Nginx configuration is correctly setting the `X-Forwarded-Proto` header to reflect the scheme used by the client. This helps in generating accurate URLs in redirects. Update your Nginx configuration as follows:
```nginx
proxy_set_header X-Forwarded-Proto $scheme;
```
2. **Enable Proxy Fix in Superset**: In your `superset_config.py`, enable the proxy fix to correctly interpret headers set by the reverse proxy. This is crucial for accurate URL generation in the 'Location' header:
```python
ENABLE_PROXY_FIX = True
PROXY_FIX_CONFIG = {"x_for": 1, "x_proto": 1, "x_host": 1, "x_port": 1, "x_prefix": 1}
```
3. **Check Redirect Configuration**: Ensure that the `Location` header in HTTP responses is correctly configured to use HTTPS. This can be managed by ensuring the `X-Forwarded-Proto` header is set correctly, as mentioned above.
These steps should help resolve the issue with incorrect redirects and the "400 Bad Request" error when accessing Superset through a reverse proxy <sup>[[1]](https://github.com/apache/superset/discussions/32757)</sup><sup>[[2]](https://github.com/apache/superset/blob/master/superset/config.py)</sup>.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=c0747639-bad2-48e7-a271-27bfa115d03d) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33440#discussioncomment-13148269
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org