Re: Recursive look up of base in outer headers

Einar Stefferud (Stef@nma.com)
Wed, 03 Sep 1997 13:19:55 -0700


To: mhtml@segate.sunet.se, uri@bunyip.com
Subject: Re: Recursive look up of base in outer headers 
In-reply-to: Your message of "Wed, 03 Sep 1997 12:11:01 PDT."
             <2FBF98FC7852CF11912A000000000001050F6D86@DINO> 
From: Einar Stefferud <Stef@nma.com>
Date: Wed, 03 Sep 1997 13:19:55 -0700
Message-ID: <9901.873317995@nma.com>

Perhaps clarity is simply obtained by noting that whenever
Content-Base and Content-Location are found to have equal predence,
the tie should be broken by giving precedence to Content-Location.

This eliminates all the concern about explaining about header sets, et
al.

It also is independent of how the tie was discovered, whether found in
the local MIME part, or by searching outward for scope.

This looks very nice and tidy to me;-)...\Stef



>From Andy Jacobs's message Wed, 3 Sep 1997 12:11:01 -0700:
}
}> The MHTML standard says that if there is both a Content-Base
}> and a Content-Location header in the same content heading, the
}> Content-Base has precedence over the Content-Location.
}
}Why not specify that if both headers exist (which is the only case where
}precedence matters) then the Base and Location headers will be combined
}according to the [RELURL] rules.  This would be consistent with the body
}part matching that already has to be done by MHTML readers.
}
}Another way of saying the same thing would be to say that Location has
}precedence if it is an absolute URL, and if it is a relative URL then it
}is combined with the Base.
}----
} - Andy Jacobs
}   andyj@microsoft.com