potiuk commented on issue #36971: URL: https://github.com/apache/airflow/issues/36971#issuecomment-1906752701
As discussed in discussion - this is something that should be done via proxy put in front of Airflow. We are note going to have all the possible bells-and-whistles that is usually provided by a dedicated proxy doing TLS termination with all the possible options such as limiting algorithms used and other specialized security behaviors, all kinds of security featyres such as rate limiting, setting up the security headers etc. Every configurability in this area we add to Airflow turns us closer to re-implementing what others (nginx, apache webserver and a dosen of dedicated proxy solutions) have already implemented. Converting it into a discussion, but we plan anyway to make it crystal clear in our documentation that in case you need such advanced features, as a Deployment Manager you are supposed to put properly configured proxy in front of airflow and use the features implemented there (basically standing on the shoulders of giants). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
