- From: Marcos Caceres <marcosc@opera.com>
- Date: Fri, 20 Nov 2009 18:31:21 +0000
- To: Marcin Hanclik <Marcin.Hanclik@access-company.com>
- Cc: WebApps WG <public-webapps@w3.org>
On Fri, Nov 20, 2009 at 11:36 AM, Marcin Hanclik
<Marcin.Hanclik@access-company.com> wrote:
> Hi Marcos,
>
>
>
> It seems I found another problem in RFC.
>
>
>
> 7.4
>
> valid-MIME-type = type "/" subtype *(";" parameter)
>
> and we refer to RFC2045 that says:
>
> [1] content := "Content-Type" ":" type "/" subtype
>
> *(";" parameter)
>
>
>
> Then, RFC2045 gives examples like:
>
> [2] Content-type: text/plain; charset=us-ascii
>
>
>
> The problem is about the spaces.
>
> As for me [2] does not match [1].
I don't know, maybe parameter allows spaces? but yeah, that first
space after "Content-type:" seems non-conforming.
>
> Anyway, it seems I can live with that issue, since it seems to affect more
> than just P&C J.
>
Me too. Lets get some implementation feedback.
> Therefore, for the purposes of my LC comments, with 99.99% certainty I will
> be satisfied with your response.
Yippy! :D
--
Marcos Caceres
http://datadriven.com.au
Received on Friday, 20 November 2009 18:32:18 UTC