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

Greg Senia commented on AMBARI-18770:
-------------------------------------

Curl Manpage:

    -L, --location
              (HTTP/HTTPS)  If the server reports that the requested page has 
moved to a different location (indicated with a Location: header and a 3XX 
response code), this
              option will make curl redo the request on the new place. If used 
together with -i, --include or -I, --head, headers from all requested  pages  
will  be  shown.
              When  authentication  is used, curl only sends its credentials to 
the initial host. If a redirect takes curl to a different host, it won't be 
able to intercept
              the user+password. See also --location-trusted on how to change 
this. You can limit the amount of redirects to follow by using the --max-redirs 
option.

              When curl follows a redirect and the request is not a plain GET 
(for example POST or PUT), it will do the following request with a GET if the 
HTTP response was
              301, 302, or 303. If the response code was any other 3xx code, 
curl will re-send the following request using the same unmodified method.

              You  can  tell  curl  to  not  change  the non-GET request method 
to GET after a 30x response by using the dedicated options for that: --post301, 
--post302 and
              -post303.


       --location-trusted
              (HTTP/HTTPS) Like -L, --location, but will allow sending the name 
+ password to all hosts that the site may redirect to. This may or may not 
introduce a  secu-
              rity breach if the site redirects you to a site to which you'll 
send your authentication info (which is plaintext in the case of HTTP Basic 
authentication).



> Service check and Ambari Alerting for RM fails against Yarn with HA and 
> SPNEGO        
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-18770
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18770
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent, ambari-server
>    Affects Versions: 2.4.0, 2.4.1, 2.4.2
>         Environment: Hortonworks HDP 2.5 and HDP 2.4
>            Reporter: Greg Senia
>            Priority: Minor
>             Fix For: 2.4.2
>
>         Attachments: AMBARI-18770.patch
>
>
> If both HA and SPNEGO is configured for the cluster, the service check and 
> ambari Alerting for RM fails for Yarn.



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

Reply via email to