http.asciidoc 2.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152
  1. [discrete]
  2. [[breaking_80_http_changes]]
  3. ==== HTTP changes
  4. //NOTE: The notable-breaking-changes tagged regions are re-used in the
  5. //Installation and Upgrade Guide
  6. //tag::notable-breaking-changes[]
  7. .The `http.content_type.required` setting has been removed.
  8. [%collapsible]
  9. ====
  10. *Details* +
  11. The `http.content_type.required` setting was deprecated in Elasticsearch 6.0
  12. and has been removed in Elasticsearch 8.0. The setting was introduced in
  13. Elasticsearch 5.3 to prepare users for Elasticsearch 6.0, where content type
  14. auto detection was removed for HTTP requests.
  15. *Impact* +
  16. Discontinue use of the `http.content_type.required` system property.
  17. Specifying this property in `elasticsearch.yml` will result in an error on
  18. startup.
  19. ====
  20. .The `http.tcp_no_delay` setting has been replaced by `http.tcp.no_delay`.
  21. [%collapsible]
  22. ====
  23. *Details* +
  24. The `http.tcp_no_delay` setting was deprecated in 7.x and has been removed in 8.0. It has been replaced by
  25. `http.tcp.no_delay`.
  26. *Impact* +
  27. Use the `http.tcp.no_delay` setting. Discontinue use of the `http.tcp_no_delay`
  28. setting. Specifying the `http.tcp_no_delay` setting in `elasticsearch.yml` will
  29. result in an error on startup.
  30. ====
  31. .The `es.rest.url_plus_as_space` system property has been removed.
  32. [%collapsible]
  33. ====
  34. *Details* +
  35. Starting in version 7.4, a `+` in a URL will be encoded as `%2B` by all REST API functionality. Prior versions handled a `+` as a single space.
  36. In these previous versions, if your application required handling `+` as a single space, you could return to the old behaviour by setting the system property
  37. `es.rest.url_plus_as_space` to `true`. Note that this behaviour is deprecated and setting this system property to `true` will cease
  38. to be supported in version 8.
  39. *Impact* +
  40. Update your workflow and applications to assume `+` in a URL is encoded as
  41. `%2B`. Discontinue use of the `es.rest.url_plus_as_space` system property.
  42. Specifying this property in `elasticsearch.yml` will result in an error on
  43. startup.
  44. ====
  45. // end::notable-breaking-changes[]