martinboksa / rest-client Goto Github PK

The groups should probably be "Safe Methods" and "Unsafe Methods", as described 
in RFC 2616: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html

But maybe we could do Idempotent and not, but that doesn't seem as useful to me.

I am proposing the following file extensions for RESTClient files:

1. Request  <-> .rcq <-> Rest Client reQuest
2. Response <-> .rcs <-> Rest Client reSponse
3. Archive  <-> .rcr <-> Rest Client aRchive

If any better option is available, please comment!

The functions of the buttons are not currently immediately apparent - I have to 
hover my mouse 
over them to see what they do. It would be better if there was text on or next 
to each button 
which indicated what they do.

The "Go" button is particularly important, and, I think, not currently 
prominent enough. I'd also 
suggest that it return to its former location at the bottom of the Request 
section - it makes sense 
sequentially, because first you'd first enter a URL, then enter options, then 
hit "Go". Also, I think 
"Send Request" was a better name than "Go".

When I open the client in Ubuntu (Feisty) some of the options get partially
covered up.  Note the attached screenshots.

Some webservices reply XML which is not formatted well for
human-readability.  The response TextArea should support a popup menu where
the user can select "Beautify", to indent the XML.

Not a big deal, but it would be really nice to support being able to resize
the UI window to be able to see more of the response when it comes back.

There's a Clear Response button, a Clear Request feature would be useful as 
well. Wouldn't have 
to be a button though, I'd think a menu item would be just fine.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

If my server is unresponsive, I have no way to cancel the request. Please add a 
Cancel button!

Thanks!

I need to load a plain request, which is headers and body; Currently i have
extract body and load it, then add each header with those buttons and text
fields..

The default font in Swing for JButton, JTabbedPane, JLabel is:

[family=Dialog,name=Dialog,style=bold,size=12]

The Bold face for all these components look offensive. Need to de-bold it.

 I entered some dummy URL(httP:://dsfdsfsdsa) without setting any proxy
details(I am working behind proxy server) and clicked send request button.
After this, button is disabled and application is keep on trying to send a
request, but it can't.

I think the semantics would be clearer if the interface would very explicitly 
identify the upper tab 
group as the "Request" group, and the lower tab group as the "Response" group. 
By using 
boxes/frames/lines to do so, it would also more visually indicate what is 
affected by the "Clear 
Response" button. The Request button should not be in either grouping, rather 
it should be in the 
middle. I'll see if I can come up with an illustration.

In the Test Script tab, above the textarea, there should be a dropdown which 
contains a list of 
templates. Users should be able to add/edit/save/delete templates. We don't 
have to necessarily 
call them templates - that might be a little off-putting for users... we could 
call them "saved 
scripts" instead, or something like that.

I'm a little unclear on the status of this method (whether it's been accepted 
as part of the HTTP 
spec or not) but it's gaining mindshare in the blogosphere (Fielding has 
written about it recently), 
so it may be worth supporting.

Here's the latest draft: 
http://www.ietf.org/internet-drafts/draft-dusseault-http-patch-11.txt

How will the Test script be compiled? The various options:

* Groovy supported

  - Supports JUnit 3.x only

* javax.tools
  ( http://www.ibm.com/developerworks/java/library/j-jcomp/index.html )

  - tools.jar may need to be bundled

* Eclipse JDT
  (
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.jdt.doc.isv/guide/jd
t_api_compile.htm
)
  - rt.jar in classpath?

RESTClient should support sending request body.

The internal API details for developers:

http://jakarta.apache.org/httpcomponents/httpclient-3.x/methods/post.html
http://www.netlikon.de/docs/commons-httpclient-3.0/apidocs/org/apache/commons/ht
tpclient/methods/PostMethod.html

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Choose the Body tab
2. Click the Edit Content-type and charset button 
3. Attempt to select one of the Atom content types defined in RFCs 4287 and
5023, for example, application/atom+xml. 

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
Version 2.1 on CentOS 5 Linux

Please provide any additional information below.
I'm not sure where the list came from, but not even application/xml is
there. The authoritative list is at
http://www.iana.org/assignments/media-types/index.html, but since it's
constantly changing, I would suggest the the UI also allow the user to
enter a value that's not in the list.

Thanks!

Sometimes when doing a testing / troubleshooting session, it can be very 
helpful to see multiple 
requests and their responses. It'd be *very* helpful if there was a Request Log 
window/pane/tab/drawer/whatever which allowed one to browse each request and 
response from 
the current session.

Once we have that, it'd also be great to have features to save the log, and 
clear the log.

This would be really handy!

This is because we get the selected row during the delete operation. When
nothing is selected, delete operation does not do anything.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

From a mail from Balasubramani S.D:

Hello Subhash,
Add proxy configuration also then it will be helpful for the users those
are working behind proxy. Just three lines of code,

System.getProperties().put( "proxySet", "true" );
System.getProperties().put( "proxyHost", "myProxyMachineName" );
System.getProperties().put( "proxyPort", "85" );

Regards,
Bala.

Preferences API should be used for storing the URLs. This will be a big
usability gain.

Currently, the keyboard shortcuts are all ctrl-X, the Mac standard is cmd-X. I 
know there's a way 
to do this, but I don't actually know what that is.

For example:

GET /path/to/resource HTTP/1.1
Host: thehost.net
Accept: */*

404 Not Found
Content-Type: text/plain
The resource could not be found.

This might be best if combined with this enhancement: 
http://code.google.com/p/rest-
client/issues/detail?id=24

What steps will reproduce the problem?
1. Select Put or Post method--the Body tab controls are now enabled
2. Open a request or request-response archive file which has Get selected
3. Go to the Body tab--the controls will be enabled.

What is the expected output? What do you see instead?

In the 3rd step above, they should not be enabled for Get request.

1. When HTTP Request headers are added--to check if the values are empty.
2. When HTTP or IOException happens--display error in debuggable format.

It would be ideal if you could add a feature that would allow me to save
the settings (including headers and body) into a "Porject". A Project
should be named after the domain name of the site being tested. A project
could contain several configs for the different resources on the site (one
for GETing Resource A, one for POSTing to Resource A, One for DELETEing
Resource B, etc;) and could all be run as a test suite against the site.

If you want to go nuts, add the ability to populate headers and body
content from a database (SQLite or XML doc or similar) so that I could run
several different body contents against the same resource settings (several
different POSTs with different entity content to the same resource, with
the settings for the Resource (auth, headers method etc;) pulled from the
Project).

That would rule. It would be trivial then to create test suites for a ReST
service, enabling developers to modify their site internals, confident that
the ReST service continues to operate for third-parties.

Cheers!

Jalf

Whilst integrating testing using Groovy/Java is great, not everyone uses
Java :)

It would be great if I could knock up some simple tests that allow me to
simply check the response from a request. Something like the following as a
file that can be saved or loaded:

[Response]
Status:200|201|404
Content-Type:application\/xml|application\/xhtml\+xml
ValidateXSD:/my/xml/schema.xsd

I should be able to use simple boolean logic and/or Regular Expressions to
check header values, and I should be able to validate the response against
an XSD or RNG file. I should be able to quickly create a test file to check
the response against. If any of the specified rules fails, I should get a
breakdown of what it was checkign, and what the actual result was.

Something nice and simple like that would be awesome (and easily
automatically generated by other tools: e.g. PHP)

Ophir requested this as comment here:

http://code.google.com/p/rest-client/wiki/TestingTutorial

i18n support is not aimed in near future. What we want is make the code
more readable by extracting bigger messages to external property file.

I have no idea how to use this feature -- there should be a way to find out 
from within the app!

Some options:
 * just add a "How to use this" link just above the text area which goes to the website
 * add some built-in help under the Help menu
 * include some default example scripts as templates, accessible via a dropdown above the 
textarea
    * hmm, that gives me an idea for another enhancement...

RESTClient should support automatic generation of this HTTP Request Header.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Is the support for ssl connections already planned? This would be very
useful when connection to https REST services.

It's not really useful to display the binary data as text.

What steps will reproduce the problem?

1. Open a .rcr file having auth details--this will enable the auth controls
including realm, uid and pwd.
2. Now open another .rcr file having no auth method selected--now also the
controls r enabled

What is the expected output? What do you see instead?

The controls should be disabled in the second step.

Might be useful for simple load testing. We'd want to be able to tweak some 
settings, such as 
how many threads to use, how long to test, and/or how many total requests to 
run.

For me this is fairly low priority, I use Charles, a web debugging proxy, which 
can already do this 
for me. But it might be pretty useful for people who don't use Charles.

http://xk72.com/charles/

Both of them should not accept duplicate keys. Validation needs to be done
before adding to JTable.

It'd be useful to have a running request timer next to the progress bar - and 
once the request is 
complete, the timer should persist, so it's easy to see how long the request 
took.

Currently you have to click the Content-type button to find out what it is. 
This can cause issues if 
you do two different type of requests sequentially; you could forget to change 
the content-type 
from one request to the next.

When teams are using the tool for testing or troubleshooting, it's really 
useful for a tester to be 
able to send a developer a single file containing a request and the response 
all together.

This will be a great usability enhancer.

This will be useful when the developer needs to save only the response body
(without the headers).

It'd be useful if I could specify a request timeout setting in the preferences. 
Not sure what the 
default should be, but it should be possible to enter 0 to indicate no timeout.

So if the user changes in the interface some request parameter, when he
saves the request, a dialog should popup saying this info so that he is
informed that he is not saving the current state of the UI, but the last
request.

This is an usability issue with the current release.

What steps will reproduce the problem?
1. Enter a URL (any url will do)
2. Select GET from the Method tab
3. Click the Body tab...all entries and buttons are disabled

What is the expected output? What do you see instead?
I would expect to be able to include a message body/entity body with a GET
request (see RESTFul Web Services by Sam Ruby, et al). This allows
providing complex input required by a resource that will not easily fit in
a query-string parameter (such as XML data)

What version of the product are you using? On what operating system?
Version 2.0 , Windows XP and Mac os x (Leopard)

Please provide any additional information below.