hzl512 / poster-extension

Automatically exported from code.google.com/p/poster-extension
0 stars 0 forks source link

HEAD, OPTIONS, and DELETE should not use GET (or could optionally for less RESTful API's) #50

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. send a HEAD request to an API (such as CouchDB Docs API) that fully
supports HEAD & GET
2. check response

What is the expected output? What do you see instead?
The response should have had only headers, but contains the GET payload
(the JSON document as the body of the response, in the CouchDB case).

What version of the product are you using? On what operating system?
2.0 on Firefox 3.6.3 on Mac OS X 10.6

Please provide any additional information below.

I'd be happy to help with the changes. It seems like a simple tweak from
handleGet('HEAD') to handleSend('HEAD') in poster.js, but I could be wrong.

Thanks.

Original issue reported on code.google.com by bigbluehat on 3 May 2010 at 2:45

GoogleCodeExporter commented 8 years ago
If the response has an entity body, the entity body will be displayed.  
Anything the server sends back is 
displayed to the user regardless of whether the 'HEAD' request is suppose to 
have an entity body.  As such, if 
there is an entity body from the response, that is the server who is doing 
things incorrectly.

If this issue is about sending an entity body on a 'HEAD' request, then this 
seems like an invalid request.

Can you please clarify what you mean and what the problem is that you are 
experiencing? 

The different between the two different javascript functions of 'handleGet' and 
'handleSend' is that the 
'handleGet' variant does not expect to *SEND* an entity body along with the 
request.  Making the change you 
suggested would essentially violate the HTTP protocol as requests like 'HEAD' 
are not suppose to have an 
entity body.

Original comment by alexmilo...@gmail.com on 3 May 2010 at 2:53

GoogleCodeExporter commented 8 years ago
Alex,

Thanks for writing back. It looks like it was a combination of caching and 
incorrect
logging with the application I was testing against. HEAD requests were being 
logged
as GET requests, and HEAD requests done after a GET request would still show the
earlier GET request body.

Glad it's not a bug in Poster. :) Keep up the great work!

Thanks,
Benjamin

Original comment by bigbluehat on 7 Jun 2010 at 12:18

GoogleCodeExporter commented 8 years ago
OK.  I'll close this out.

Original comment by alexmilo...@gmail.com on 7 Jun 2010 at 1:20