Closed yawen-QvQ closed 3 years ago
@Aallam can you review? Also, what do we think about just replacing the existing browse
method to use POST instead of GET? Do you expect that to break anything?
Hi @benwaffle and @yawen-QvQ, thank you for your PR! I don't expect this won't break anything, if we look at Java client implementation, it uses POST and it works as expected.
I've created a fork of this PR (#622) to run the CI.
Describe your change Replace the existing browse GET request with browse POST. When the query to too long, GET request returns 414.