Adding a custom header to HTTP request using angular.js

前端 未结 8 1767
说谎
说谎 2020-11-27 13:01

I am a novice to angular.js, and I am trying to add some headers to a request:

   var config = {headers: {
            \'Authorization\': \'Basic d2VudHdvcnR         


        
相关标签:
8条回答
  • 2020-11-27 13:20

    I took what you had, and added another X-Testing header

    var config = {headers:  {
            'Authorization': 'Basic d2VudHdvcnRobWFuOkNoYW5nZV9tZQ==',
            'Accept': 'application/json;odata=verbose',
            "X-Testing" : "testing"
        }
    };
    
    $http.get("/test", config);
    

    And in the Chrome network tab, I see them being sent.

    GET /test HTTP/1.1
    Host: localhost:3000
    Connection: keep-alive
    Accept: application/json;odata=verbose
    X-Requested-With: XMLHttpRequest
    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.172 Safari/537.22
    Authorization: Basic d2VudHdvcnRobWFuOkNoYW5nZV9tZQ==
    X-Testing: testing
    Referer: http://localhost:3000/
    Accept-Encoding: gzip,deflate,sdch
    Accept-Language: en-US,en;q=0.8
    Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
    

    Are you not seeing them from the browser, or on the server? Try the browser tooling or a debug proxy and see what is being sent out.

    0 讨论(0)
  • 2020-11-27 13:25

    What you see for OPTIONS request is fine. Authorisation headers are not exposed in it.

    But in order for basic auth to work you need to add: withCredentials = true; to your var config.

    From the AngularJS $http documentation:

    withCredentials - {boolean} - whether to to set the withCredentials flag on the XHR object. See requests with credentials for more information.

    0 讨论(0)
  • 2020-11-27 13:26

    my suggestion will be add a function call settings like this inside the function check the header which is appropriate for it. I am sure it will definitely work. it is perfectly working for me.

    function getSettings(requestData) {
        return {
            url: requestData.url,
            dataType: requestData.dataType || "json",
            data: requestData.data || {},
            headers: requestData.headers || {
                "accept": "application/json; charset=utf-8",
                'Authorization': 'Bearer ' + requestData.token
            },
            async: requestData.async || "false",
            cache: requestData.cache || "false",
            success: requestData.success || {},
            error: requestData.error || {},
            complete: requestData.complete || {},
            fail: requestData.fail || {}
        };
    }
    

    then call your data like this

        var requestData = {
            url: 'API end point',
            data: Your Request Data,
            token: Your Token
        };
    
        var settings = getSettings(requestData);
        settings.method = "POST"; //("Your request type")
        return $http(settings);
    
    0 讨论(0)
  • 2020-11-27 13:26

    Chrome is preflighting the request to look for CORS headers. If the request is acceptable, it will then send the real request. If you're doing this cross-domain, you will simply have to deal with it or else find a way to make the request non-cross-domain. This is by design.

    Unlike simple requests (discussed above), "preflighted" requests first send an HTTP request by the OPTIONS method to the resource on the other domain, in order to determine whether the actual request is safe to send. Cross-site requests are preflighted like this since they may have implications to user data. In particular, a request is preflighted if:

    It uses methods other than GET, HEAD or POST. Also, if POST is used to send request data with a Content-Type other than application/x-www-form-urlencoded, multipart/form-data, or text/plain, e.g. if the POST request sends an XML payload to the server using application/xml or text/xml, then the request is preflighted. It sets custom headers in the request (e.g. the request uses a header such as X-PINGOTHER)

    Ref: AJAX in Chrome sending OPTIONS instead of GET/POST/PUT/DELETE?

    0 讨论(0)
  • 2020-11-27 13:26

    For me the following explanatory snippet worked. Perhaps you shouldn't use ' for header name?

    {
       headers: { 
          Authorization: "Basic " + getAuthDigest(), 
          Accept: "text/plain" 
       }
    }
    

    I'm using $http.ajax(), though I wouldn't expect that to be a game changer.

    0 讨论(0)
  • 2020-11-27 13:34

    Basic authentication using HTTP POST method:

    $http({
        method: 'POST',
        url: '/API/authenticate',
        data: 'username=' + username + '&password=' + password + '&email=' + email,
        headers: {
            "Content-Type": "application/x-www-form-urlencoded",
            "X-Login-Ajax-call": 'true'
        }
    }).then(function(response) {
        if (response.data == 'ok') {
            // success
        } else {
            // failed
        }
    });
    

    ...and GET method call with header:

    $http({
        method: 'GET',
        url: '/books',
        headers: {
            'Authorization': 'Basic d2VudHdvcnRobWFuOkNoYW5nZV9tZQ==',
            'Accept': 'application/json',
            "X-Login-Ajax-call": 'true'
        }
    }).then(function(response) {
        if (response.data == 'ok') {
            // success
        } else {
            // failed
        }
    });
    
    0 讨论(0)
提交回复
热议问题