Re: [httpwg/http-extensions] Serialization for structured headers. (#627)
HTTP issue updates <http-issues@ietf.org> Fri, 25 May 2018 13:13 UTC
Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Date: Fri, 25 May 2018 06:13:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527254012; bh=wrlfeD2xdtQZqbmXRB7gXQpznEjSaHJ8oFHyV+Uvh9I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dFAQJeqz5JQl1ICAshac6vQZNMOPQq0UTH6v3PYINBycwlLX7OONAznpEtLZxQUJN isrjDS75rrneV9BMQIQb/z/vNGg9Ah3U2ZLRZCiYltIYy70cFpZkoOdGuwj3y3yxwa HrQY02y6ONNxX6oM36AnD1t0uiuzgDKpT/mpcZ6U=
To: httpwg/http-extensions <http-extensions@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
In-Reply-To: <httpwg/http-extensions/issues/627@github.com>
References: <httpwg/http-extensions/issues/627@github.com>
Subject: Re: [httpwg/http-extensions] Serialization for structured headers. (#627)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b080bfc41a08_3f303fa75bc18f8092747"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-issues/uJiJoDqkoytvE2hWLuFw4zBL4sc>
Message-ID: <mailman.986.1527254015.2697.http-issues@ietf.org>
From: HTTP issue updates <http-issues@ietf.org>
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates <http-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-issues>, <mailto:http-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-issues/>
List-Post: <mailto:http-issues@ietf.org>
List-Help: <mailto:http-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-issues>, <mailto:http-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2018 13:13:35 -0000
@mnot - actually, what's in a HTTP/1.1 message should also be better considered a byte sequence, not a string @mikewest - I would prefer to have SH not to rely on FETCH in any way -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/627#issuecomment-392053750
- [httpwg/http-extensions] Serialization for struct… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates
- Re: [httpwg/http-extensions] Serialization for st… HTTP issue updates