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

Steve Loughran commented on YARN-2605:
--------------------------------------

Can it just send a 307 "resubmit same verb" response to the caller? That will 
be picked up by browsers and handled as a new GET, while REST clients 
(including curl, jersey, htttpclient) will either GET or resubmit the original 
verb depending on their config.

Sending a custom structured response won't work with those existing clients

> [RM HA] Rest api endpoints doing redirect incorrectly
> -----------------------------------------------------
>
>                 Key: YARN-2605
>                 URL: https://issues.apache.org/jira/browse/YARN-2605
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.4.0
>            Reporter: bc Wong
>              Labels: newbie
>
> The standby RM's webui tries to do a redirect via meta-refresh. That is fine 
> for pages designed to be viewed by web browsers. But the API endpoints 
> shouldn't do that. Most programmatic HTTP clients do not do meta-refresh. I'd 
> suggest HTTP 303, or return a well-defined error message (json or xml) 
> stating that the standby status and a link to the active RM.
> The standby RM is returning this today:
> {noformat}
> $ curl -i http://bcsec-1.ent.cloudera.com:8088/ws/v1/cluster/metrics
> HTTP/1.1 200 OK
> Cache-Control: no-cache
> Expires: Thu, 25 Sep 2014 18:34:53 GMT
> Date: Thu, 25 Sep 2014 18:34:53 GMT
> Pragma: no-cache
> Expires: Thu, 25 Sep 2014 18:34:53 GMT
> Date: Thu, 25 Sep 2014 18:34:53 GMT
> Pragma: no-cache
> Content-Type: text/plain; charset=UTF-8
> Refresh: 3; url=http://bcsec-2.ent.cloudera.com:8088/ws/v1/cluster/metrics
> Content-Length: 117
> Server: Jetty(6.1.26)
> This is standby RM. Redirecting to the current active RM: 
> http://bcsec-2.ent.cloudera.com:8088/ws/v1/cluster/metrics
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to