Make JSONP versus GET an option for Solr, default to JSONP #495
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.
Description
New functionality to allow you to specific GET instead of JSONP for the apiMethod to Solr. If you have a API that is mimicking Solr, well, you don't need the JSONP if you hvae proper cors support. THis can simplify some folks lives
Motivation and Context
Baby step towards supporting the Solr V2 API (which is JSON POST), and introduces into the wizard a option to have settings for a serach engine.
In the future maybe we share a search engine with a Team, so thers can pick from a list...
How Has This Been Tested?
Screenshots or GIFs (if appropriate):
Types of changes
Checklist: