Oh, I understand, but either a request IS or IS NOT idempotent, and the fact that a client sends a HEAD request is NOT what determines that!
The point is that HEAD is fairly useless with dynamic web applications. Its just the nature of the beast. Proper up-front cache-control is where you really have to deal with things. Sometimes you can use HEAD to your advantage though. I guess the upshot is that (getting back to the original point ) there is no one proper way to do it, some HEADs should replay the entire request, others shouldn't. > The HTTP book defines HEAD as behaving exactly the same as GET but > without the entity body > being returned. > > If your content is being served via the cache, it's trivial. If your > content is > dynanmic then your gonna have to do what ever you would have done for > the GET. > > GET's should not have side effects anyway. > > > Mike. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Tod Harter Giant Electronic Brain http://www.giantelectronicbrain.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
