W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > February 2009

RE: http-request content-type and encoding

From: <Toman_Vojtech@emc.com>
Date: Wed, 4 Feb 2009 08:00:17 -0500
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870E6BC2E2@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-comments@w3.org>

> Suppose I want to send a MIME multipart request where the first part
> is encoding as UTF-8 and the second part is encoded as ISO-8859-1.
> Do I do this:
>   <c:multipart ...>
>     <c:body content-type="application/xml" 
> encoding="utf-8">...</c:body>
>     <c:body content-type="application/xml" 
> encoding="iso-8859-1">...</c:body>
>   </c:multipart>
> or do I do this:
>   <c:multipart ...>
>     <c:body content-type="application/xml; charset=utf-8">...</c:body>
>     <c:body content-type="application/xml; 
> charset=iso-8859-1">...</c:body>
>   </c:multipart>

I would say the latter, because that would allow, in theory, for things

<c:multipart ...>
  <c:body content-type="application/xml; charset=utf-8"
  <c:body content-type="application/xml; charset=iso-8859-1"

That is, you can have both a charset and an encoding.

> or have we not considered this case?
> Our current description of the encoding attribute only mandates
> support for "base64".
> It would appear that 'encoding' on p:http-request applies to the
> entire body, but in the multipart case, that may not be correct.

By saying 'the entire body', do you mean the entire c:multipart in this
case? I think that is not how it is supposed to work. The way I
understand it is that you can have a c:multipart with 10 c:body parts,
and 5 of them base64 encoded.

Or did I misunderstand you?

Received on Wednesday, 4 February 2009 13:01:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:26 UTC