Re: p:http-request content-type and encoding

• From: Florent Georges <fgeorges@fgeorges.org>
• Date: Tue, 10 Feb 2009 18:09:53 +0100
• To: Norman Walsh <ndw@nwalsh.com>
• Cc: public-xml-processing-model-comments@w3.org
• Message-ID: <ebaca5bf0902100909s1182738ana77d1920d48d26cc@mail.gmail.com>

2009/2/4 Florent Georges wrote:

>  If I am right, base64 is different yet.  This is defined in RFC
> 1521, p. 14 <http://tools.ietf.org/html/rfc1521#page-14>:

>    encoding := "Content-Transfer-Encoding" ":" mechanism

>    mechanism :=     "7bit"  ;  case-insensitive
>                   / "quoted-printable"
>                   / "base64"
>                   / "8bit"
>                   / "binary"
>                   / x-token

  But I've seen that the RFC for HTTP 1.1 says in section
19.4.5 <http://tools.ietf.org/html/rfc2616#section-19.4.5>:

    HTTP does not use the Content-Transfer-Encoding (CTE) field
    of RFC 2045.  Proxies and gateways from MIME-compliant
    protocols to HTTP MUST remove any non-identity CTE
    ("quoted-printable" or "base64") encoding prior to
    delivering the response message to an HTTP client.

  So it seems base64 does not even make sense in c:body/@encoding...  Any idea?

  Regards,

-- 
Florent Georges
http://www.fgeorges.org/

Received on Tuesday, 10 February 2009 17:10:29 UTC