[
https://issues.apache.org/jira/browse/AIRFLOW-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020280#comment-17020280
]
Mathieu Poussin edited comment on AIRFLOW-3806 at 1/21/20 2:55 PM:
-------------------------------------------------------------------
Any update on this ? This is quite critical, I could not find a way to deploy
Airflow correctly behind a reverse proxy because of those redirect (that
redirect to the Host that is not reachable by the end users so the whole UI is
broken, instead of honoring base_url)
was (Author: kedare):
Any update on this ? This is quite critical, I could not find a way to deploy
Airflow correctly behind a reverse proxy because of those redirect (that
redirect to the Host that is not reachable by the end users so the whole UI is
broken)
> Redirects use absolute URLs (and ignore base_url)
> -------------------------------------------------
>
> Key: AIRFLOW-3806
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3806
> Project: Apache Airflow
> Issue Type: Bug
> Components: webserver
> Affects Versions: 1.10.2
> Reporter: Stanislaw Pitucha
> Priority: Major
>
> I'm having an issue deploying airflow behind a load balancer where the user's
> connection is terminated using https, but then forwarded to airflow using
> http.
> For some reason the redirect from path "/" uses the current domain and forced
> http port. This seems to both:
> * ignore the base_url
> * use the full domain where only a relative location would be enough
> I see there's AIRFLOW-571 open to address the similar problem, but it seems
> like a very specific workaround rather than a fix for sending the wrong
> redirect in the first place.
> HTTP 302 allows relative redirect, so for example "/" -> "/admin/" should
> work just fine without the domain name or the schema. If the absolute path is
> desired, it should use "base_url" as defined in the config file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
