A.M. Kuchling wrote:
> That's not clear; the RFC says for 201 "The response SHOULD include an
> entity containing a list of resource characteristics and location(s)
> from which the user or user agent can choose the one most
> appropriate", with the most specific location given in the Location:
> header.  To me, that implies an HTML/XML body listing locations.

Interesting-- I didn't notice that.  It seems redundant to me since the
Location header exists to indicate the new resource location.  In my
application only one resource is ever returned, and you do a GET on it
to find out its status.

I guess that's why it's a SHOULD and not a MUST.

-John


--
http:// if   l .o  /