[
https://issues.apache.org/jira/browse/AIRFLOW-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535302#comment-16535302
]
ASF subversion and git services commented on AIRFLOW-1163:
----------------------------------------------------------
Commit a8dd6d86d512af2dcaf77270b18f2f6366bff5e6 in incubator-airflow's branch
refs/heads/master from Camilo Aguilar
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=a8dd6d8 ]
[AIRFLOW-1163][AIRFLOW-XXX] Add support for x-forwarded-* headers
When running Airflow behind a L7 proxy that sends
x-fowarded-* headers, the Flask app miscontructs
redirect URIs.
Closes #3580 from c4milo/master
> Cannot Access Airflow Webserver Behind AWS ELB
> ----------------------------------------------
>
> Key: AIRFLOW-1163
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1163
> Project: Apache Airflow
> Issue Type: Bug
> Affects Versions: Airflow 1.7.1
> Reporter: Tim
> Priority: Major
>
> Cannot access airflow from behind a load balancer.
> If we go directly to the IP of the server it loads just fine. When trying to
> use the load balancer cname and forward the request it does not load.
> We updated the base_url to be the LB url but it still does not work. The page
> sits and spins forever. Eventually it loads some ui elements.
> Here is what I see on the network tab:
> https://puu.sh/vC4Zp/e388884131.png
> Here is what our config looks like:
> {code}
> [webserver]
> # The base url of your website as airflow cannot guess what domain or
> # cname you are using. This is use in automated emails that
> # airflow sends to point links to the right web server
> base_url =
> http://internal-st-airflow-lb-590109685.us-east-1.elb.amazonaws.com:80
> # The ip specified when starting the web server
> web_server_host = 0.0.0.0
> # The port on which to run the web server
> web_server_port = 8080
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
