concept remote server in category cors

This is an excerpt from Manning's book CORS in Action: Creating and consuming cross-origin APIs.
In the same way that you want money from your bank account, the client wants data from the server. The client is a snippet of JavaScript code running on a website, and it’s responsible for initiating the CORS request. It’s served from a particular domain and usually consists of an XMLHttpRequest to a remote server. The following code snippet highlights the portion from the sample’s client.html file that is responsible for making the CORS request:
A curl-like interface to send CORS requests to a remote server. This can be useful for testing actual CORS requests from a browser against your server.
The first way to use test-cors.org is to send cross-origin requests to a remote server. This is similar to how curl works, but it makes its request from the browser using an XMLHttpRequest object, rather than the command line. This can be helpful because it makes an HTTP request the same way you’d expect a client. For example, curl will let you add a Host header to the request. But the Host header can’t be set from test-cors.org, because the browser controls this header.