RE: Recursive look up of base in outer headers

"Andy Jacobs (Exchange)" <> Wed, 03 September 1997 19:25 UTC

Received: from cnri by id aa17616; 3 Sep 97 15:25 EDT
Received: from (services.Bunyip.Com []) by (8.8.5/8.7.3) with ESMTPid PAA00186; Wed, 3 Sep 1997 15:28:31 -0400 (EDT)
Received: (from daemon@localhost) by (8.8.5/8.8.5) id PAA28401 for uri-out; Wed, 3 Sep 1997 15:11:15 -0400 (EDT)
Received: from (mocha.Bunyip.Com []) by (8.8.5/8.8.5) with ESMTP id PAA28396 for <>; Wed, 3 Sep 1997 15:11:12 -0400 (EDT)
Received: (from daemon@localhost) by (8.8.5/8.8.5) id PAA25143 for uri@services; Wed, 3 Sep 1997 15:08:37 -0400 (EDT)
Received: from ( []) by (8.8.5/8.8.5) with SMTP id PAA25140 for <uri@Bunyip.Com>; Wed, 3 Sep 1997 15:08:33 -0400 (EDT)
Received: by DOGGATE with Internet Mail Service (5.5.1664.3) id <R7R1N43W>; Wed, 3 Sep 1997 12:11:05 -0700
Message-ID: <2FBF98FC7852CF11912A000000000001050F6D86@DINO>
From: "Andy Jacobs (Exchange)" <>
To: 'Jacob Palme' <>, Al Gilman <>
Subject: RE: Recursive look up of base in outer headers
Date: Wed, 3 Sep 1997 12:11:01 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1664.3)
Content-Type: text/plain
Precedence: bulk

> 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