Jason Lowe commented on YARN-3239:

the WebProxyServlet does support appending the client-provided path and query 
strings, as I can verify it by simply curling a regular MapReduce app's proxy 
URL.  For example:

$ curl 
      Content has moved 

However it does not properly handle URI fragments supplied by either the app or 
the client, and it doesn't honor query parameters set in the tracking URL by 
the app.

Thanks for the patch, Jian!  Patch looks good overall, and merging query 
strings between the client and the app-specified URL seems reasonable.  However 
it doesn't look like we're honoring any fragments provided by the client, and 
that would break clients for any app UIs that generate fragment-containing 

> WebAppProxy does not support a final tracking url which has query fragments 
> and params 
> ---------------------------------------------------------------------------------------
>                 Key: YARN-3239
>                 URL: https://issues.apache.org/jira/browse/YARN-3239
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>            Assignee: Jian He
>         Attachments: YARN-3239.1.patch
> Examples of failures:
> Expected: 
> {{http://uihost:8080/#/main/views/TEZ/}}
> Actual: {{http://uihost:8080}}
> Tried with a minor change to remove the "#". Saw a different issue:
> Expected: 
> {{http://uihost:8080/views/TEZ/}}
> Actual: {{http://uihost:8080/views/TEZ/}}
> yarn application -status appId returns the expected value correctly. However, 
> invoking an http get on http://rm:8088/proxy/appId/ returns the wrong value. 

This message was sent by Atlassian JIRA

Reply via email to