Remove coercion of Console GET requests to POST #39170
Closed
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.
To-do
Verify all of these on master, then create tests for them:
See if this affects [Console] Autocomplete support for read only users #36635
Streaming large responses (should be handled by lib)
Limited user permissions
Error response (e.g. ES is down)
HEAD /?pretty=true
HEAD request
HEAD twitter/_doc/0
Test on
https
and ensureagent
has intended effect. What aboutrejectUnauthorized
? Did it ever actually work? ([console] support HEAD requests #10611)DELETE with body works (https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-scroll.html)
cat format is preserved
Send body with GET
Fixes original problem of returning an error when a GET is inappropriately sent with a body
Ensure
proxyConfig
andproxyFilters
still work (https://www.elastic.co/guide/en/kibana/5.0/configuring-console.html)In master, we should remove support for
proxyConfig
andproxyFilters
(#11670, #9823).Alternative solution
This alternative uses the
http
Node library which is more low-level but removes the need for therequest
dependency.