How to determine server's decoding capability before sending entity?
"Yi, EungJun" <semtlenori@gmail.com> Fri, 15 February 2013 07:12 UTC
Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92B3621F8971 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 14 Feb 2013 23:12:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RYzUV9hCab70 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 14 Feb 2013 23:12:26 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 20FE521F86D9 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 14 Feb 2013 23:12:26 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1U6FRx-0000O4-Sg for ietf-http-wg-dist@listhub.w3.org; Fri, 15 Feb 2013 07:11:13 +0000
Resent-Date: Fri, 15 Feb 2013 07:11:13 +0000
Resent-Message-Id: <E1U6FRx-0000O4-Sg@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <semtlenori@gmail.com>) id 1U6FRq-0000NB-FI for ietf-http-wg@listhub.w3.org; Fri, 15 Feb 2013 07:11:06 +0000
Received: from mail-ie0-f173.google.com ([209.85.223.173]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <semtlenori@gmail.com>) id 1U6FRp-0001xc-S0 for ietf-http-wg@w3.org; Fri, 15 Feb 2013 07:11:06 +0000
Received: by mail-ie0-f173.google.com with SMTP id 9so4329404iec.32 for <ietf-http-wg@w3.org>; Thu, 14 Feb 2013 23:10:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:date:message-id:subject:from:to :content-type; bh=98jF2m/UxLZx5LpbS26uDCH97clQaF7PJh9Jp+/8kN0=; b=dAte1B+uazOisiziUfqrZqgYyxD0KsVPdEc94Qc9++NrnmITvp+Q5x15wTmCOkumNo Os8RUOHDJTSIdAslcz3HZWUqfaq5VHt6IqiZL3MUwY+E32mZQkwLF3o4JGa9tNynXt7w eXqdMrDbGEyiquntNHidytpoYcStrJpBuB50jXcjio9LsIHusT5WCDoV83q1wUOtaoEV D6rD5Dw1NAdGOvaAPE6ILnudPG7/iwPuIOpwFbQAyF38GK1kC9wAvYQVHYqsnLJouNPN TyOLIeMDnbqOJpiwZJgg/NixnpG6W72lhl1x5/6l7TDu/zY1t5JBAKllF706uePFurwO nBRQ==
MIME-Version: 1.0
X-Received: by 10.42.67.10 with SMTP id r10mr986252ici.7.1360912239967; Thu, 14 Feb 2013 23:10:39 -0800 (PST)
Received: by 10.50.208.105 with HTTP; Thu, 14 Feb 2013 23:10:39 -0800 (PST)
Reply-To: semtlenori@gmail.com
Date: Fri, 15 Feb 2013 16:10:39 +0900
Message-ID: <CAFT+Tg-oyYrS53mObRVVFKL2z0WxAXmzjdcdLJazs277noYVEQ@mail.gmail.com>
From: "Yi, EungJun" <semtlenori@gmail.com>
To: ietf-http-wg@w3.org
Content-Type: multipart/alternative; boundary="20cf3030bd29a23fb204d5be126e"
Received-SPF: pass client-ip=209.85.223.173; envelope-from=semtlenori@gmail.com; helo=mail-ie0-f173.google.com
X-W3C-Hub-Spam-Status: No, score=-2.7
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1U6FRp-0001xc-S0 33b2bef99247da6400919967aefa1a7e
X-Original-To: ietf-http-wg@w3.org
Subject: How to determine server's decoding capability before sending entity?
Archived-At: <http://www.w3.org/mid/CAFT+Tg-oyYrS53mObRVVFKL2z0WxAXmzjdcdLJazs277noYVEQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16610
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Hi, all. Before sending a POST request to HTTP/1.1 server, whose body is encoded in the coding defined by Content-Encoding header, how do I know the server's capability to decode the request's body? HEAD method seems to be only for GET method, and response for OPTIONS request may not return any information about that. It is the only way that receive 415 Unsupported media type after sending the request with the body? Thanks in advance.
- Re: How to determine server's decoding capability… Amos Jeffries
- How to determine server's decoding capability bef… Yi, EungJun