Julian,
Great, thanks for extracting the related HTTP specification. I previously
missed this important point.
As an aside, I've added an RFE to support this extension in the Restlet API:
http://restlet.tigris.org/issues/show_bug.cgi?id=285
Best regards,
Jerome
> -----Message d'origine-----
> De : Julian Reschke [mailto:julian.reschke_at_gmx.de]
> Envoyé : mardi 10 avril 2007 14:03
> À : dev_at_jsr311.dev.java.net
> Objet : Re: Parsing headers, was: Abstract from HTTP <was>
> Re: Welcome to JSR 311
>
> Jerome Louvel schrieb:
> >>> I would suggest the following approach:
> >>>
> >>> public void setTags(@Context("header.Slug") List<String> tags){
> >>> ...
> >>> }
> >> You lost me here. "Slug" is not of type list...
> >
> > Sorry, I wrongly assumed that "Slug" was a repeating
> header. Let's consider
> > this solution for a truly repeating header instead.
> >
> > RFC2047:
> >> It adds the ability to represent non-ISO8859 characters in headers.
> >
> > OK. Is it compatible with the HTTP 1.1 specification of headers?
> >
> > Best regards,
> > Jerome
>
> HTTP/1.1 says in
> <http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.2.2.p.7>:
>
> "The TEXT rule is only used for descriptive field contents and values
> that are not intended to be interpreted by the message
> parser. Words of
> *TEXT MAY contain characters from character sets other than
> ISO-8859-1
> [22] only when encoded according to the rules of RFC 2047 [14]."
>
> Best regards, Julian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
>