Hi Rajkumar, I think it would be ok to set the Location header. Because if there is an explicite check-in by the client, the server must set this header. Also HTTP 1.1 only says about the response headers the following:
--- snip (RFC2616 6.2)---- The response-header fields allow the server to pass additional information about the response which cannot be placed in the Status- Line. These header fields give information about the server and about further access to the resource identified by the Request-URI. --- snip ----- So I will set it, if there aren't any objections. regards, Mathias > -----Original Message----- > From: Raj Kumar [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 19, 2001 11:21 PM > To: [EMAIL PROTECTED] > Subject: RE: version controlled resources and version resources > > > hi mathias, > Maybe i should clarify on the question about obtaining the > version given the > uri to the version-controlled-resource. > I understood the mechanism you used to generate the URI for > the version > given the URI for the version-controlled-resource and the > version number. > But how can a client obtain the URI for a revision given the > URI for the > version-controlled-resource.In other words when you automatically do a > checkout\checkin on a resource when the client issues a > proppatch or a put > request do you return the URI of the created version in the > Location Header > for the client to use it? > thanks, > rajkumar
