HEAD, OPTIONS, and DELETE should not use GET (or could optionally for less RESTful API's) about poster-extension HOT 3 CLOSED

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.

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

OK.  I'll close this out.