@@ -182,7 +182,7 @@ SSL and Authentication
182
182
~~~~~~~~~~~~~~~~~~~~~~
183
183
184
184
You can configure the client to use ``SSL `` for connecting to your
185
- elasticsearch cluster, including certificate verification and http auth::
185
+ elasticsearch cluster, including certificate verification and HTTP auth::
186
186
187
187
from elasticsearch import Elasticsearch
188
188
@@ -245,12 +245,12 @@ Environment considerations
245
245
When using the client there are several limitations of your environment that
246
246
could come into play.
247
247
248
- When using an http load balancer you cannot use the :ref: `sniffing `
248
+ When using an HTTP load balancer you cannot use the :ref: `sniffing `
249
249
functionality - the cluster would supply the client with IP addresses to
250
250
directly connect to the cluster, circumventing the load balancer. Depending on
251
251
your configuration this might be something you don't want or break completely.
252
252
253
- In some environments (notably on Google App Engine) your http requests might be
253
+ In some environments (notably on Google App Engine) your HTTP requests might be
254
254
restricted so that ``GET `` requests won't accept body. In that case use the
255
255
``send_get_body_as `` parameter of :class: `~elasticsearch.Transport ` to send all
256
256
bodies via post::
@@ -260,13 +260,13 @@ bodies via post::
260
260
261
261
Compression
262
262
~~~~~~~~~~~
263
- When using capacity constrained networks (low throughput), it may be handy to enable
263
+ When using capacity- constrained networks (low throughput), it may be handy to enable
264
264
compression. This is especially useful when doing bulk loads or inserting large
265
265
documents. This will configure compression on the *request *.
266
266
::
267
267
268
268
from elasticsearch import Elasticsearch
269
- es = Elasticsearch(hosts, http_compress = True)
269
+ es = Elasticsearch(hosts, http_compress= True)
270
270
271
271
272
272
Running on AWS with IAM
0 commit comments