This repository has been archived by the owner on Feb 5, 2024. It is now read-only.
Switching to POST request and encoding "keys" in POST body when "keys" p... #18
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
|
Just hit the same problem. I'm fetching a view with about a hundred of keys, and client crashed with out of memory error. POST request works correctly. |
|
The same problem guys. |
beberlei
added a commit
that referenced
this pull request
Nov 11, 2015
Switching to POST request and encoding "keys" in POST body when "keys" p...
beberlei
added a commit
that referenced
this pull request
Nov 11, 2015
beberlei
added a commit
that referenced
this pull request
Nov 11, 2015
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Switching to POST request and encoding "keys" in POST body when "keys" parameter is present.
Using a keys query array as query param in a GET request does not seem to work very well (At least for me working with a BigCouch instance the keys are ignored completely). The CouchDb documentation suggests to use a POST request with the requested keys encoded in the post body (this works in my setup).