Re: [Axis2] Use of correct case for MIME headers
"Thilina Gunarathne" <[email protected]>
| Newsgroups | gmane.text.xml.axis.devel,gmane.text.xml.commons.devel |
|---|---|
| Message-ID | <[email protected]> |
Done... On 4/4/07, Alexander Veit <[email protected]> wrote: > Thilina Gunarathne wrote: > > Hi all, > > When sending MIME messages Axis2 sets the mime part headers as > > "content-type" & "content-id" which are incorrect according to the [1] > > & [2]. They should be "Content-Type" and "Content-ID" respectively. > > Sending Content-Type and Content-ID seems to be a good idea > > RFC 2616 HTTP/1.1 states that > > "4.2 Message Headers > HTTP header fields, which include general-header (section 4.5), > request-header (section 5.3), response-header (section 6.2), and > entity-header (section 7.1) fields, follow the same generic format as > that given in Section 3.1 of RFC 822. Each header field consists of a > name followed by a colon (":") and the field value. Field names are > case-insensitive." > > As far as I know neither RFC 2045 nor RFC 2822 define field names to be > case sensitive. However, to maximize interoperability, it's probably the > best practice to use the notation given in the respective standards. > > > Shall I go ahead and make the change in Axiom.. .. > > +1 from me. > > -- > Regards, > Alex > > > Sorry if you get this mail twice. The first seemed not to get through... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com