You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by Thilina Gunarathne <cs...@gmail.com> on 2007/04/03 12:11:29 UTC

[Axis2] Use of correct case for MIME headers

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.

Shall I go ahead and make the change in Axiom.. ..

Thilina.
[1] http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
[2] http://www.ietf.org/rfc/rfc2392.txt

-- 
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org

Re: [Axis2] Use of correct case for MIME headers

Posted by Saminda Abeyruwan <sa...@gmail.com>.
 Even in mail transport headers, RFC says headers should be named as you
mentioned. Like "Content-Disposition".

+1

Saminda

On 4/3/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
>
> +1!
>
> Paul Fremantle wrote:
> > +1
> >
> >
> > On 4/3/07, Davanum Srinivas <da...@gmail.com> wrote:
> >> I guess so... +1
> >>
> >> -- dims
> >>
> >> On 4/3/07, Thilina Gunarathne <cs...@gmail.com> 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.
> >> >
> >> > Shall I go ahead and make the change in Axiom.. ..
> >> >
> >> > Thilina.
> >> > [1] http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
> >> > [2] http://www.ietf.org/rfc/rfc2392.txt
> >> >
> >> > --
> >> > Thilina Gunarathne  -  http://www.wso2.com -
> >> http://thilinag.blogspot.com
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> >> > For additional commands, e-mail: commons-dev-help@ws.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
> >> Developers
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Saminda Abeyruwan

Software Engineer
WSO2 Inc. - www.wso2.org

Re: [Axis2] Use of correct case for MIME headers

Posted by Glen Daniels <gl...@thoughtcraft.com>.
+1!

Paul Fremantle wrote:
> +1
> 
> 
> On 4/3/07, Davanum Srinivas <da...@gmail.com> wrote:
>> I guess so... +1
>>
>> -- dims
>>
>> On 4/3/07, Thilina Gunarathne <cs...@gmail.com> 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.
>> >
>> > Shall I go ahead and make the change in Axiom.. ..
>> >
>> > Thilina.
>> > [1] http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
>> > [2] http://www.ietf.org/rfc/rfc2392.txt
>> >
>> > --
>> > Thilina Gunarathne  -  http://www.wso2.com - 
>> http://thilinag.blogspot.com
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: commons-dev-help@ws.apache.org
>> >
>> >
>>
>>
>> -- 
>> Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services 
>> Developers
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Use of correct case for MIME headers

Posted by Paul Fremantle <pz...@gmail.com>.
+1


On 4/3/07, Davanum Srinivas <da...@gmail.com> wrote:
> I guess so... +1
>
> -- dims
>
> On 4/3/07, Thilina Gunarathne <cs...@gmail.com> 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.
> >
> > Shall I go ahead and make the change in Axiom.. ..
> >
> > Thilina.
> > [1] http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
> > [2] http://www.ietf.org/rfc/rfc2392.txt
> >
> > --
> > Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: commons-dev-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Use of correct case for MIME headers

Posted by Davanum Srinivas <da...@gmail.com>.
I guess so... +1

-- dims

On 4/3/07, Thilina Gunarathne <cs...@gmail.com> 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.
>
> Shall I go ahead and make the change in Axiom.. ..
>
> Thilina.
> [1] http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
> [2] http://www.ietf.org/rfc/rfc2392.txt
>
> --
> Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Use of correct case for MIME headers

Posted by Davanum Srinivas <da...@gmail.com>.
I guess so... +1

-- dims

On 4/3/07, Thilina Gunarathne <cs...@gmail.com> 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.
>
> Shall I go ahead and make the change in Axiom.. ..
>
> Thilina.
> [1] http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
> [2] http://www.ietf.org/rfc/rfc2392.txt
>
> --
> Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org

Re: [Axis2] Use of correct case for MIME headers

Posted by Davanum Srinivas <da...@gmail.com>.
SAAJ Specification is inconsistent with itself...with it's RI and with
it's TCK. See [1] for details.

-- dims

[1] http://blogs.cocoondev.org/dims/archives/004755.html

On 4/4/07, sumedha rubasinghe <su...@gmail.com> wrote:
> Which one is correct? 'Content-ID' or 'Content-Id '??
>
> In SAAJ specification it is referred as 'Contend-Id'.
> https://*saaj*.dev.java.net/spec-*1.3*/*saaj*13.pdf
>
> /sumedha
>
>
> On 4/3/07, Thilina Gunarathne <cs...@gmail.com> 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.
> >
> > Shall I go ahead and make the change in Axiom.. ..
> >
> > Thilina.
> > [1] http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
> > [2] http://www.ietf.org/rfc/rfc2392.txt
> >
> > --
> > Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: commons-dev-help@ws.apache.org
> >
> >
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org

Re: [Axis2] Use of correct case for MIME headers

Posted by Thilina Gunarathne <cs...@gmail.com>.
AFAIK Content-ID is the correct one.. See the section 2 of [1]..

Thanks,
Thilina
[1] http://www.ietf.org/rfc/rfc2392.txt

On 4/4/07, sumedha rubasinghe <su...@gmail.com> wrote:
> Which one is correct? 'Content-ID' or 'Content-Id '??
>
> In SAAJ specification it is referred as 'Contend-Id'.
> https://*saaj*.dev.java.net/spec-*1.3*/*saaj*13.pdf
>
> /sumedha
>
>
> On 4/3/07, Thilina Gunarathne <cs...@gmail.com> 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.
> >
> > Shall I go ahead and make the change in Axiom.. ..
> >
> > Thilina.
> > [1] http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
> > [2] http://www.ietf.org/rfc/rfc2392.txt
> >
> > --
> > Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: commons-dev-help@ws.apache.org
> >
> >
>


-- 
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org

Re: [Axis2] Use of correct case for MIME headers

Posted by sumedha rubasinghe <su...@gmail.com>.
Which one is correct? 'Content-ID' or 'Content-Id '??

In SAAJ specification it is referred as 'Contend-Id'.
https://*saaj*.dev.java.net/spec-*1.3*/*saaj*13.pdf

/sumedha


On 4/3/07, Thilina Gunarathne <cs...@gmail.com> 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.
>
> Shall I go ahead and make the change in Axiom.. ..
>
> Thilina.
> [1] http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
> [2] http://www.ietf.org/rfc/rfc2392.txt
>
> --
> Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
>
>

Re: [Axis2] Use of correct case for MIME headers

Posted by Thilina Gunarathne <cs...@gmail.com>.
Done...

On 4/4/07, Alexander Veit <al...@dev.unitedplanet.de> 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: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
>
>


-- 
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Use of correct case for MIME headers

Posted by Thilina Gunarathne <cs...@gmail.com>.
Done...

On 4/4/07, Alexander Veit <al...@dev.unitedplanet.de> 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: commons-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: commons-dev-help@ws.apache.org
>
>


-- 
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org

Re: [Axis2] Use of correct case for MIME headers

Posted by Alexander Veit <al...@dev.unitedplanet.de>.
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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org

Re: [Axis2] Use of correct case for MIME headers

Posted by Deepal jayasinghe <de...@gmail.com>.
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.
>
> Shall I go ahead and make the change in Axiom.. ..

Yes , please do so b4 1.2.3 release.

Thanks
Deepal

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org