Search SDK: Add POST support to Search and Suggest #1384
Merged
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.
The Azure Search REST API now supports making Search and Suggest requests
using HTTP POST instead of GET. Some customers have very large queries that
won't fit on the URL query string. POST gives them the choice to put their
queries in the request body instead.
This PR changes the behavior of the Search SDK to use POST instead of GET for
Search and Suggest calls, unless the caller sets the UseHttpGetForQueries
property on ISearchIndexClient. It also splits SearchTests and SuggestTests
into separate derived classes that exercise both POST and GET variations. This
required re-recording all the mock session records.