You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Susheel Gupta (Jira)" <ji...@apache.org> on 2026/01/23 06:41:00 UTC

[jira] [Commented] (YARN-11923) YARN web proxy AmIpFilter allows TRACE, bypassing sparkUI TRACE block

    [ https://issues.apache.org/jira/browse/YARN-11923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053799#comment-18053799 ] 

Susheel Gupta commented on YARN-11923:
--------------------------------------

Steps to repro:

1. Start Spark on YARN:
   spark3-shell --conf spark.master=yarn
2. Send TRACE to Spark UI:
    curl -v -X TRACE http://<hostname>:4040
3. We observe HTTP 302 found.

> YARN web proxy AmIpFilter allows TRACE, bypassing sparkUI TRACE block
> ---------------------------------------------------------------------
>
>                 Key: YARN-11923
>                 URL: https://issues.apache.org/jira/browse/YARN-11923
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>            Reporter: Susheel Gupta
>            Assignee: Susheel Gupta
>            Priority: Major
>
> In yarn mode, sparkUI responds to http TRACE with 302 redirect. The redirect happens in AmIpFilter, so the TRACE request is getting processed before spark jetty handler can reject it. This causes security scanners to report TRACE enabled.
> In local mode there is no yarn proxy filter, so requests go directly to spark Jetty servlet. SPARK‑5983 adds TRACE filter correctly returning 405.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org