Jason Tedor 1df43a09b7 Remove HTTP max content length leniency (#29337) ... I am not sure why we have this leniency for HTTP max content length, it has been there since the beginning (5ac51ee93f) with no explanation of its source. That said, our philosophy today is different than the philosophy of the past where Elasticsearch would be quite lenient in its handling of settings and today we aim for predictability for both users and us. This commit removes leniency in the parsing of http.max_content_length.		2018-04-02 20:20:01 -04:00
..
cluster	…
discovery	…
indices	…
scripting	…
cluster.asciidoc	…
cross-cluster-search.asciidoc	…
discovery.asciidoc	…
gateway.asciidoc	…
http.asciidoc	…
indices.asciidoc	…
memcached.asciidoc	…
network.asciidoc	…
node.asciidoc	…
plugins.asciidoc	…
scripting.asciidoc	…
snapshots.asciidoc	…
threadpool.asciidoc	…
thrift.asciidoc	…
transport.asciidoc	…