7520a107be
This change adds a strict mode for xcontent parsing on the rest layer. The strict mode will be off by default for 5.x and in a separate commit will be enabled by default for 6.0. The strict mode, which can be enabled by setting `http.content_type.required: true` in 5.x, will require that all incoming rest requests have a valid and supported content type header before the request is dispatched. In the non-strict mode, the Content-Type header will be inspected and if it is not present or not valid, we will continue with auto detection of content like we have done previously. The content type header is parsed to the matching XContentType value with the only exception being for plain text requests. This value is then passed on with the content bytes so that we can reduce the number of places where we need to auto-detect the content type. As part of this, many transport requests and builders were updated to provide methods that accepted the XContentType along with the bytes and the methods that would rely on auto-detection have been deprecated. In the non-strict mode, deprecation warnings are issued whenever a request with body doesn't provide the Content-Type header. See #19388 |
||
|---|---|---|
| .. | ||
| cat.asciidoc | ||
| cluster.asciidoc | ||
| docs.asciidoc | ||
| indices.asciidoc | ||
| ingest.asciidoc | ||
| mappings.asciidoc | ||
| percolator.asciidoc | ||
| plugins.asciidoc | ||
| rest.asciidoc | ||
| scripting.asciidoc | ||
| search.asciidoc | ||
| settings.asciidoc | ||
| stats.asciidoc | ||