ACTION-492 Review Larry's health warning on redirection to secondary resources and either agree or fix

This is regarding HTTP WG Issue 43 (which we've been discussing).
http://trac.tools.ietf.org/wg/httpbis/trac/ticket/43

I agree with Larry's health warning. Therefore this action item is discharged.

[comments: 1. I don't think interpretation of fragids is in the
jurisdiction of HTTP. 2. I don't want anyone to demand that #B
*always* be dropped from A#B when A redirects to C#D.  Maybe OK in
browser situations.]

Following is the 'health warning' in question. (But I don't like
"fragment combination" which is not an appropriate description of
what's going on.)

masinter: (4) You can have one fragment id, but not two.
masinter: You can do this, but something might break.
masinter (reworded by jar): If you deploy a 30x Location: C#D, then be
aware that anyone who creates a URI A#B, might be inconvenienced
(since there are no fragment combination rules).

masinter: Opposed to telcon time on this

ACTION-491 - Schedule telcon attempt to formulate health warning on
secondary resource redirection noting Larry proposal in 21 Oct 2010
F2F record [on Noah Mendelsohn - due 2010-10-28].
ACTION-492 - Review Larry's health warning on redirection to secondary
resources and either agree or fix [on Jonathan Rees - due 2010-10-28].

Jonathan

Received on Friday, 29 October 2010 20:57:30 UTC