Lines Matching refs:to
4 This page contains the information you need to connect and use the Client with
17 This section contains code snippets to show you how to connect to various {es}
24 You can connect to Elastic Cloud using **Basic authentication**:
35 are generated when you deploy a new cloud instance. You need to store the
49 equivalent to Base64(<id>:<key>). You need to store the API key since it will
57 If your {es} server is protected by HTTP authentication, you need to provide the
58 credentials to ES-PHP so that requests can be authenticated server-side.
74 Credentials are provided per-host, which allows each host to have their own set
75 of credentials. All requests sent to the cluster use the appropriate credentials
76 depending on the node being talked to.
84 {ref-7x}/security-api-create-api-key.html[here], you can use these values to
101 Configuring SSL is a little more complex. You need to identify if your
108 If you believe the client is configured to correctly use SSL, but it simply is
111 the `--cacert` option was not added to the OSX version of libcurl until version
112 7.37.1. The `--cacert` option is equivalent to PHP's `CURLOPT_CAINFO` constant,
124 server has up-to-date root certificates, you only need to use `https` in the
140 If your server has out-dated root certificates, you may need to use a
141 certificate bundle. For PHP clients, the best way is to use
143 need to tell the client to use your certificates instead of the system-wide
144 bundle. To do this, specify the path to verify:
164 yourself. It should not be used when being exposed to public consumers, since
165 this leaves the client vulnerable to man-in-the-middle attacks.
167 If you are using a self-signed certificate, you need to provide the certificate
168 to the client. This is the same syntax as specifying a new root bundle, but
169 instead you point to your certificate:
174 $myCert = 'path/to/cacert.pem';
187 It is possible to use HTTP authentication with SSL. Simply specify `https` in
195 $myCert = 'path/to/cacert.pem';
209 allows you a smoother upgrade experience from 7 to 8. In a nutshell, you can use
211 room to coordinate the upgrade of your codebase to the next major version.
213 If you want to leverage this functionality, please make sure that you are using the
215 to `true`. The client is handling the rest internally. For every 8.0 and beyond
241 To index a document, we need to specify three pieces of information: index, id
244 pairs corresponding to the data in your document:
295 `_source` field, which is the original document you sent to {es}.
318 Searching is a hallmark of {es}, so let's perform a search. We are going to use
395 This syntax is identical to the `get` syntax. The only difference is the
415 Due to the dynamic nature of {es}, the first document you added automatically