On Tuesday, July 29, 2003, at 06:52 pm, Tod Harter wrote:
Well...
You've essentially run into one of the problems with the HTTP house of cards!
There really is no clear way to deal with it either. HEAD was a nice theory,
and it works fine for static content that gets updated now-and-then. But for
non-idempotent requests (which in theory should always be POSTs) there just
is no real way to work it. Either you DO perform the entire request, in which
case HEAD is potentially non-idempotent and takes on the same characteristics
as a POST (but remember, you cannot tell which method the server would
normally expect, GET or POST from a HEAD...).
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]
