PadmajaPeri opened a new issue, #25776:
URL: https://github.com/apache/airflow/issues/25776

   ### Apache Airflow version
   
   Other Airflow 2 version
   
   ### What happened
   
   We are running airflow version 2.3.1 behind an apache proxy. The base_url in 
the webserver in airflow.cfg is as below - 
   
   [webserver]
   # The base url of your website as airflow cannot guess what domain or
   # cname you are using. This is used in automated emails that
   # airflow sends to point links to the right web server. `airflow` is 
appended at
   # the end so that authz regex can be defined off of this path
   base_url = https://<host_name>/airflow
   
   On the airflow DAGs page, when I click on "Last Run" (for a DAG) and copy 
the link address, I see that a https link is generated - 
   https://<host_name>/airflow/graph?dag_id=<dag_id>&execution_date=<some_date>
   
   However, when I load the link, the response is empty. The reason is, the 
link has been transformed into http as below
   
   http://<host_name>/airflow/dags/<dag_id>/graph?execution_date=<some_date>
   
   ### What you think should happen instead
   
   The returned link should be a https link since the server is running on https
   
   ### How to reproduce
   
   1. Run airflow on https behind a proxy
   2. Click on Last Run
   
   
   ### Operating System
   
   Ubuntu Bionic (18.04LTS)
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   _No response_
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to