Then you can call back gourl after the success of the getData method to perform the logical processing you want
In addition, I don’t know how to judge your is_success specifically because there is $ajax and a corresponding error

Your code is equivalent to executing the following two sentences:

location.href = '../exit.html';
location.href = 'http://www.baidu.com';

When these two sentences are executed continuously, they will jump to the following address

My guess is that it takes time for the browser to access the first one, but before it succeeds, the second jump comes again, so I give up the first jump and execute the second jump, similar to quickly entering the address twice in the URL. Same.

The

gourl() function cannot be called in front, but should be placed in the middle of the Ajax logic, and add else{gourl();}
that is:

if (!is_success) {
        location.href = "../exit.html";
    }else {
        gourl();
    }

The code of the questioner can be understood as follows:

    <script type="text/javascript">
    $(function() {
        getData();
    });

    function getData() {
        var is_success = false;
        $.ajax({
            type: "GET",
            url: "http://baike.baidu.com/api/openapi/BaikeLemmaCardApi?scope=103&format=json&appid=379020&bk_key=bug&bk_length=600",
            data: "",
            dataType: "json",
            async: false,
            success: function(data) {
                if (data.status == 200) {
                    is_success = true;
                } else {
                    is_success = false;
                }
            },
            error: function() { ... }
        });
        if (!is_success) {
            location.href = "../exit.html";
        }
        console.log('我被执行了');
        window.location.href = 'http://www.baidu.com';
    }
    </script>

When there are two consecutive location.hrefs in the code, the subsequent jump will be executed. The subject of this question can try it himself.

In addition, since ajax is asynchronous, the subject needs to write if(!is_success) into the error in ajax, or into the else judgment in success, otherwise it will jump regardless of whether ajax is successful or not. gourl() should also be written into success.

In addition, cross-domain errors should occur if ajax is used directly like this. It is recommended to use a proxy or other methods to solve cross-domain problems.

Mobile phone code, is this what you mean?

$(function() {
    var dtd = $.Deferred();
    dtd
      .done(function(){
          console.log('我被执行了');
          window.location.href = 'http://www.baidu.com';
      })
      .fail(function(){
          console.log('我被抛弃了');
          window.location.href = "../exit.html";
      });
    $.get("http://baike.baidu.com/api/openapi/BaikeLemmaCardApi?scope=103&format=json&appid=379020&bk_key=bug&bk_length=600", "json")
      .done(function(data) {
          if (data.status == 200) {
              dfd.resolve();
          } else {
              dtd.reject();
          }
      });
});

Mainly using jQ’s promises, all written asynchronously, all successful callbacks of ajax are placed in the done of Deferred (if there are multiple, they can also be written as arrays), and then just give a status directly in the done of ajax.

Since getData and gourl have an execution relationship, either gourl is placed in the callback judgment. This can be suitable for asynchronous use.
If it’s synchronization with the subject, then it’s okay

    $(function() {
        getData();
        gourl();
    });

Can I control Gourl directly here to execute it?

There may be something wrong with your code logic. Ajax is asynchronous. gourl(); This function should not be called in that place. It can be called in the success or failure callback of the ajax request.
Looking at your request, it should be called in success.