Apache Airflow version
Other Airflow 3 version (please specify below)
If "Other Airflow 3 version" selected, which one?
3.1.3
What happened?
The extra link generated by TriggerDagRunLink (the “Triggered DAG” button) builds a UI URL without honoring base_url setting.
When Airflow is running behind a reverse proxy on a subpath (e.g. /airflow/), the link breaks.
What you think should happen instead?
Extra links should use the same base URL logic documented for reverse proxy deployments.
The reverse proxy guide specifically shows that Airflow must use base_url for correct link generation.
How to reproduce
- Run Airflow UI behind a prefix, e.g. https://myhost/myorg/airflow/
- Use TriggerDagRunOperator
- After the task completes, open Task Details → Extra links
- Click Triggered DAG → browser attempts to open /dags/... instead of /myorg/airflow/dags/...
Operating System
Red Hat Enterprise Linux 8.10
Versions of Apache Airflow Providers
No response
Deployment
Virtualenv installation
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
Apache Airflow version
Other Airflow 3 version (please specify below)
If "Other Airflow 3 version" selected, which one?
3.1.3
What happened?
The extra link generated by TriggerDagRunLink (the “Triggered DAG” button) builds a UI URL without honoring base_url setting.
When Airflow is running behind a reverse proxy on a subpath (e.g. /airflow/), the link breaks.
What you think should happen instead?
Extra links should use the same base URL logic documented for reverse proxy deployments.
The reverse proxy guide specifically shows that Airflow must use base_url for correct link generation.
How to reproduce
Operating System
Red Hat Enterprise Linux 8.10
Versions of Apache Airflow Providers
No response
Deployment
Virtualenv installation
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct