This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/v3-1-test by this push:
     new a3bbd8feb38 [v3-1-test] Fix message of _read_from_logs_server when 
status_code is 403 (#59489) (#59504)
a3bbd8feb38 is described below

commit a3bbd8feb38bdf86ecdf4eae6bcbcecd41648a63
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Tue Dec 16 17:05:21 2025 +0100

    [v3-1-test] Fix message of _read_from_logs_server when status_code is 403 
(#59489) (#59504)
    
    (cherry picked from commit 97b30f412b228b8ac989cc875234539c4afc852a)
    
    Co-authored-by: nhuantho <[email protected]>
    Co-authored-by: nhuan.bc <[email protected]>
---
 airflow-core/src/airflow/utils/log/file_task_handler.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/airflow-core/src/airflow/utils/log/file_task_handler.py 
b/airflow-core/src/airflow/utils/log/file_task_handler.py
index 3b90d94afbc..ae02f579e82 100644
--- a/airflow-core/src/airflow/utils/log/file_task_handler.py
+++ b/airflow-core/src/airflow/utils/log/file_task_handler.py
@@ -880,8 +880,8 @@ class FileTaskHandler(logging.Handler):
             if response.status_code == 403:
                 sources.append(
                     "!!!! Please make sure that all your Airflow components 
(e.g. "
-                    "schedulers, webservers, workers and triggerer) have "
-                    "the same 'secret_key' configured in 'webserver' section 
and "
+                    "schedulers, api-servers, dag-processors, workers and 
triggerer) have "
+                    "the same 'secret_key' configured in '[api]' section and "
                     "time is synchronized on all your machines (for example 
with ntpd)\n"
                     "See more at 
https://airflow.apache.org/docs/apache-airflow/";
                     "stable/configurations-ref.html#secret-key"

Reply via email to