Body Tab not enabled for GET requests

[GoogleCodeExporter]

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.

Original issue reported on code.google.com by fulle...@gmail.com on 22 Feb 2008 at 7:37

[GoogleCodeExporter]

I should also note that this is not a POST operation...I am inherently 
requesting
safe GET type data, but need to provide complex qualifiers.

Original comment by fulle...@gmail.com on 22 Feb 2008 at 7:39

[GoogleCodeExporter]

This is a strange issue. I have never come across a non-POST/PUT Request having 
a
Body. Anyway, I will try to get my basics right, and also see if the underlying 
HTTP
library used by RESTClient (Commons HTTP 3.x) supports this.

Original comment by subwiz on 23 Feb 2008 at 4:22

[GoogleCodeExporter]

I have RESTful WebServices book. Can u tell me the chapter/pages which talk 
about
body content in GET request?

Original comment by subwiz on 23 Feb 2008 at 6:02

[GoogleCodeExporter]

It appears that my lack of HTTP conventions have misled me here...when the 
author made the statement that 
"the lack of a body was *typical* of a GET request" (emphasis mine), I made the 
leap assuming that though it did 
not typically have one, that a GET request *could* have a body if needed.  As 
I've looked at various HTTP library 
implementations since my post here, however, it seems that at least by 
convention no one does this.  My 
apologies for the errant feature request.

Original comment by fulle...@gmail.com on 25 Feb 2008 at 7:07

[GoogleCodeExporter]

Thanks @fullercr! I am closing this issue...

Original comment by subwiz on 26 Feb 2008 at 1:00

• Changed state: Invalid