Re: remaining redirect ref issues

WRT to the open redirect issues:

Julian wrote on 11/06/2003 06:57:53 AM:

> The main remaining issues are listed at after the TOC:
> 
> - get rid of MKRESOURCE if favor of a simpler method that can only 
> create redirect reference resources; this should also allow to *update* 
> redirect reference resources (with a new target)

I agree.

> - allow authoring of 301s as well,

I agree.

> - finish the synchronization between RFC2518bis and the redirect ref 
> spec on how PROPFIND should behave when a collection contains redirect 
> references

Are there issues here, or is this just editorial?

> - almost all other issues are editorial or about terminology -- 
> proposals how to resolve these (replacement text!) are welcome

Probably the best thing here is to start a thread on these issues,
along with your current proposed solution, so we can bring them to
closure.

> Another issue that's not listed yer:
> 
> - COPY applied to a collection containing redirect refs currently is 
> specified not to copy the redirects (unless the client explicitly 
> specifies that using "Apply-To-Redirect-Ref"). Thus, non-redirect-ref 
> aware clients will always get a 207 (that is, only a partial success) 
> when attempting the COPY. We should consider allowing he COPY to succeed 

> if the server is able to recreate an equivalent redirect reference at 
> the target.

I agree.  We should just state this.

Cheers,
Geoff