[widgets] LCWD#3 comments (3)

2009-11-20 Thread Marcin Hanclik
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;

RE: [widgets] LCWD#3 comments (3)

2009-11-20 Thread Marcin Hanclik
: public-webapps-requ...@w3.org [mailto:public-webapps-requ...@w3.org] On Behalf Of Marcin Hanclik Sent: Friday, November 20, 2009 12:36 PM To: WebApps WG Subject: [widgets] LCWD#3 comments (3) Hi Marcos, It seems I found another problem in RFC. 7.4 valid-MIME-type = type / subtype *(; parameter

Re: [widgets] LCWD#3 comments (3)

2009-11-20 Thread Marcos Caceres
On Fri, Nov 20, 2009 at 11:36 AM, Marcin Hanclik marcin.hanc...@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    

Re: [widgets] LCWD#3 comments (3)

2009-11-20 Thread Marcos Caceres
From: marcosscace...@gmail.com [marcosscace...@gmail.com] On Behalf Of Marcos Caceres [marc...@opera.com] Sent: Friday, November 20, 2009 7:31 PM To: Marcin Hanclik Cc: WebApps WG Subject: Re: [widgets] LCWD#3 comments (3) On Fri, Nov 20, 2009 at 11:36 AM, Marcin

RE: [widgets] LCWD#3 comments (3)

2009-11-20 Thread Marcin Hanclik
: WebApps WG Subject: Re: [widgets] LCWD#3 comments (3) On Nov 20, 2009, at 8:24 PM, Marcin Hanclik marcin.hanc...@access-company.com wrote: Hi Marcos, I don't know, maybe parameter allows spaces? but yeah, that first space after Content-type: seems non-conforming. RFC2045: parameter