Erik Hetzner <erik.hetzner <at> ucop.edu> writes: > > Are you saying there's some place in Restlet where the entity is striped > > out in the case of HEAD? You might be right, although I didn't see it. > > Regardless, that makes unreasonable assumptions about the intent for > > HEAD. > > I don’t know; it just seems to me that the place for the optimization > which doesn’t call the code that returns the content of the response > when we have a HEAD instead of a GET belongs there, not in a special > case in your Resource.
Here's an interesting follow-up. I have a resource that only implements GET and returns "Ok". As the code implies, a HEAD request will do just like GET. When I run: curl --request head <my-url> It blocks until timeout and then prints: curl: (18) transfer closed with 2 bytes remaining to read So it seems the esteemed tool, curl, totally expects HEAD to not return any content. Sean
