apiblueprint.org
apiblueprint.org copied to clipboard
Double-encoding of url query parameters
In our apiary.io documentation http://docs.g2crowdapi.apiary.io/# we have one endpoint defined as such: /v1/products{?filter%5Bquery%5D,page%5Bnumber%5D,page%5Bsize%5D}
The problem is that when testing the endpoint in the console, the query parameters are encoded again which in turn submits a different request than desired.
I'm having the same issue. I believe this should be supported as it is a recommendation of the JSON API spec. Any word on this?