[DOCS] Low Level REST Client should emphasize ContentType #22940
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds a callout to note that the Low Level REST Client example sets the `ContentType` explicitly and that users should do the same.
pickypg
added
:Clients/Java Low Level REST Client
javanna
approved these changes
Feb 3, 2017
pickypg
added a commit
that referenced
this pull request
Feb 4, 2017
This adds a callout to note that the Low Level REST Client example sets the `ContentType` explicitly and that users should do the same.
pickypg
added a commit
that referenced
this pull request
Feb 4, 2017
This adds a callout to note that the Low Level REST Client example sets the `ContentType` explicitly and that users should do the same.
pickypg
added a commit
that referenced
this pull request
Feb 4, 2017
This adds a callout to note that the Low Level REST Client example sets the `ContentType` explicitly and that users should do the same.
pickypg
added a commit
that referenced
this pull request
Feb 4, 2017
This adds a callout to note that the Low Level REST Client example sets the `ContentType` explicitly and that users should do the same.
|
master/6.0: d2428b1 (removal of last sentence) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a callout to note that the Low Level REST Client example sets the
ContentTypeexplicitly and that users should do the same (ContentTypeis required by all of theHttpEntity's that I am aware of, but it's not required to be set properly).I will drop the
Future releases of Elasticsearch will require this to be set properly.sentence from the master branch in a follow-up commit.Relates to #19388