Introduction
This document lists the limitations of RESTClient.
Details
- Support for binary content. This is not present, and is not planned for the near future. Only UTF-8 supported charset content can be loaded in the Request Body text pane.
- HTTP Headers values cannot have newlines.
File not in supported encoding (UTF-8) java.io.IOException: File not in supported encoding (UTF-8)
Caused by: java.nio.charset.MalformedInputException?: Input length = 1The GET method greys out parameters. But some of the REST services I see expect an argument to follow GET as far as I can tell. Can you illuminate?
AFAIK, only POST and PUT support body. Even the HTTP API I use (Apache HTTP Client) does not support it.
Here's an example from AWS where they're expecting a GET parameter:
http://docs.amazonwebservices.com/AWSSimpleQueueService/2006-04-01/REST_RestServiceGET.html
I assume you could just add it to the URI as a question mark followed by a query string, but that kind of defeats the point of having a friendly client. :)
Yes, many social networking (blog, etc.) APIs expect to be able to tell them what you want to get. Can we make this easier in rest-client? Is it a simple edit I could try within the source?
The Amazon example sends the parameters in URL, not in Body of the request. Only POST and PUT support Body element. So I understand from @ksenzee that you want a dialog (like the one available in Body tab) for entering the parameters, which will be finally appended to the URL? Is that correct?
Would it really be that hard to add support for binary format of body? Seams you could simply disallow manual editing and only allow loading from a file in that case. If you wanted to get fancy you could display a hex dump of the binary data, but if I'm just loading from a file, I can do my own hex dumps if that's what I'm after.
I too would welcome the support for binary format of Request.Body Not being able to use this feature sort of defeats the purpose of otherwise very nice REST testing tool. Yep, just disable the edit window and instead of hex dump you could display only some basic information on uploaded file, like filename (with or without full path) and its size in bytes. Thanks again for your work on RESTClient!