[apps-discuss] 'Base' and 'Content-Base' header fields
Mykyta Yevstifeyev <evnikita2@gmail.com> Mon, 29 August 2011 15:53 UTC
Return-Path: <evnikita2@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D5D21F8839 for <apps-discuss@ietfa.amsl.com>; Mon, 29 Aug 2011 08:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.461
X-Spam-Level:
X-Spam-Status: No, score=-3.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pE7YDcKoCTOQ for <apps-discuss@ietfa.amsl.com>; Mon, 29 Aug 2011 08:53:22 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9764D21F87C5 for <apps-discuss@ietf.org>; Mon, 29 Aug 2011 08:53:22 -0700 (PDT)
Received: by fxe6 with SMTP id 6so4964082fxe.31 for <apps-discuss@ietf.org>; Mon, 29 Aug 2011 08:54:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=GcOuNctj6vRBgJJbEvSwxfSdZt8uji/jztgxyhBckDs=; b=f5GRXUGwHZsQcc+TGeyld1JdypZzTm2A637/FUQDC4PqFlIkFZl0+GfbsAOSTrTBH9 7FYmkHc4T1yXlLq1PrrVM4x022fMz0Hqt3ZwaaJKGKyQ7rpk+MYinsF0APh74u7/L7dS x5BFsWJLulnFgLjZbqZhqfhy2wr9FeZkFTXjE=
Received: by 10.223.88.193 with SMTP id b1mr7402283fam.40.1314633286917; Mon, 29 Aug 2011 08:54:46 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id c7sm3858005fac.12.2011.08.29.08.54.46 (version=SSLv3 cipher=OTHER); Mon, 29 Aug 2011 08:54:46 -0700 (PDT)
Message-ID: <4E5BB666.60903@gmail.com>
Date: Mon, 29 Aug 2011 18:55:18 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Apps-discuss list <apps-discuss@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] 'Base' and 'Content-Base' header fields
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 15:53:23 -0000
Hello all, RFC 1808 proposed the 'Base' header field to be used in HTTP/mail messages. This header field was intended to be used for establishing the base URI when resolving relative URIs; what RFC 1808 says is: > Messages are considered to be composite documents. The base URL of a > message can be specified within the message headers (or equivalent > tagged metainformation) of the message. For protocols that make use > of message headers like those described in RFC 822 [5], we recommend > that the format of this header be: > > base-header = "Base" ":" "<URL:" absoluteURL ">" > > where "Base" is case-insensitive and any whitespace (including that > used for line folding) inside the angle brackets is ignored. However, this disappeared from RFC 2396. RFC 2110, though, introduced 'Content-Base' header field for the similar purpose, but RFC 2557, which obsoleted 2110, said that this header field was removed from the new version of MHTML. Now 'Content-Base' for MIME is listed with reference to RFC 4021, which referred to then-obsoleted RFC 2110. RFC 4229 registered 'Content-Base' for HTTP, referring to RFC 2068. Nevertheless RFC 2616 didn't specify 'Content-Base' header field as well, so the factual spec is obsolete RFC 2068. So, you see, 'Content-Base' is in the rather uncertain state, and no clear definition is available. (This reminds me of 'Link' header field, which was in rather the same state.) So, is there enough support to undertake the effort to define 'Content-Base' field properly? Mykyta Yevstifeyev
- [apps-discuss] 'Base' and 'Content-Base' header f… Mykyta Yevstifeyev
- Re: [apps-discuss] 'Base' and 'Content-Base' head… Frank Ellermann
- Re: [apps-discuss] 'Base' and 'Content-Base' head… Murray S. Kucherawy
- Re: [apps-discuss] 'Base' and 'Content-Base' head… SM
- Re: [apps-discuss] 'Base' and 'Content-Base' head… Frank Ellermann
- Re: [apps-discuss] 'Base' and 'Content-Base' head… Mark Nottingham