[
https://issues.apache.org/jira/browse/AIRFLOW-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884024#comment-16884024
]
ASF subversion and git services commented on AIRFLOW-4934:
----------------------------------------------------------
Commit 93a3d5993e6b55a6410a3bc160d90fd7ac11e440 in airflow's branch
refs/heads/v1-10-test from Nathaniel Ritholtz
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=93a3d59 ]
[AIRFLOW-4934] Bump Flask to resolve Werkzeug ProxyFix (#5571)
(cherry picked from commit 2c3243566779108343156a9ce83b58d2aff495f1)
> ProxyFix not working as expected since Werkzeug v0.15
> -----------------------------------------------------
>
> Key: AIRFLOW-4934
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4934
> Project: Apache Airflow
> Issue Type: Bug
> Components: webserver
> Affects Versions: 1.10.3
> Reporter: Nathaniel Ritholtz
> Assignee: Nathaniel Ritholtz
> Priority: Major
> Fix For: 1.10.4
>
>
> Since Werkzeug 0.15, _enable_proxy_fix_ doesn't work as expected as per [this
> Github issue|https://github.com/pallets/werkzeug/issues/1484].
> We should fix it to at least respect what was previous behavior. We can
> eventually also offer a configuration to customize the new behavior, however
> this is breaking old behavior, and is required within the next/current
> release due to the Flask pin.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
