RE: Issue: Requiring server to use / terminated URL for returned collections

   From: Jason Crawford []

   I think the remaining issues are...

   Were there truly some interop issues with not always returning a
   trailing slash?  What were they?  Would a requirement of
   consistancy work just as well as requiring a terminating slash?

   Certain broken behaviors in existing clients/servers was mentioned.
   What products, people, etc do we need to follow up with?

   Can a client assume that, if a server returns a URL that ends in a
   slash, the resource referenced is a collection?

I would have no problem with that requirement, if it can be 
demonstrated to have significant client value.


Received on Wednesday, 25 September 2002 11:49:29 UTC