Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message
Raghu, If you look at http://www.w3.org/TR/SOAP-attachments, RFC 2045 and RFC 822, you can see that the Content-ID field and also the start part of the Content-Type field don't conform to the specifications. It is therefore not so surprising that Axis rejects the message. Maybe you should post a message to a .NET related forum about this problem. Regards, Andreas On 11 Jan 2008, at 19:00, Raghu Kasturi wrote: Hi, When I try to send the soap message using my .net Client to Axis2 service, I get the following exception: Creating an Attachments map. The content-length is6984 2008-01-11 10:39:37,184 DEBUG AxisServlet org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: FaultTo is null. Returning isReplyRedirected 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: ReplyTo is null. Returning false 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true My Soap Message is: OST /soapAdapter/services/myTestService HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2407) SOAPAction: PostRq Content-Type: Multipart/Related; boundary=5a21e1d7- c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 Content-Length: 6984 Connection: Keep-Alive Host: hostname:8090 --5a21e1d7-c13a-414f-856b-1d8db8caec7a Content-Type: text/xml Content-Transfer-Encoding: binary Content-ID: dd5584d3-dfbc-4a0a-94a9-11be8726f446 ?xml version=1.0 encoding=utf-8?soap:Envelope …. / soap:Envelope Please help me in this regards. Thanks, Raghu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message
Raghu, If this was the origin of the problem, you should open a JIRA issue, because RFC 2045 says that All media type values, subtype values, and parameter names as defined are case-insensitive. Regards, Andreas On 11 Jan 2008, at 20:44, Raghu Kasturi wrote: Hi Andreas, Thanks for the reply. I could fix the issue, there were two problems in my SOAP message which Axis2 was not able to handle it. Content-Type: Multipart/Related; boundary=5a21e1d7-c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 One: Multipart/Related should be multipart/related (Axis2 doesn't handle it) Two: Text/xml should be text/xml (Axis2/ Axiom should handle it) Thanks, Raghu -Original Message- From: Andreas Veithen [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 12:40 PM To: axis-user@ws.apache.org Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Raghu, If you look at http://www.w3.org/TR/SOAP-attachments, RFC 2045 and RFC 822, you can see that the Content-ID field and also the start part of the Content-Type field don't conform to the specifications. It is therefore not so surprising that Axis rejects the message. Maybe you should post a message to a .NET related forum about this problem. Regards, Andreas On 11 Jan 2008, at 19:00, Raghu Kasturi wrote: Hi, When I try to send the soap message using my .net Client to Axis2 service, I get the following exception: Creating an Attachments map. The content-length is6984 2008-01-11 10:39:37,184 DEBUG AxisServlet org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: FaultTo is null. Returning isReplyRedirected 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: ReplyTo is null. Returning false 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true My Soap Message is: OST /soapAdapter/services/myTestService HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2407) SOAPAction: PostRq Content-Type: Multipart/Related; boundary=5a21e1d7- c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 Content-Length: 6984 Connection: Keep-Alive Host: hostname:8090 --5a21e1d7-c13a-414f-856b-1d8db8caec7a Content-Type: text/xml Content-Transfer-Encoding: binary Content-ID: dd5584d3-dfbc-4a0a-94a9-11be8726f446 ?xml version=1.0 encoding=utf-8?soap:Envelope / soap:Envelope Please help me in this regards. Thanks, Raghu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message
Hi Andreas, Thanks for the reply. I could fix the issue, there were two problems in my SOAP message which Axis2 was not able to handle it. Content-Type: Multipart/Related; boundary=5a21e1d7-c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 One: Multipart/Related should be multipart/related (Axis2 doesn't handle it) Two: Text/xml should be text/xml (Axis2/ Axiom should handle it) Thanks, Raghu -Original Message- From: Andreas Veithen [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 12:40 PM To: axis-user@ws.apache.org Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Raghu, If you look at http://www.w3.org/TR/SOAP-attachments, RFC 2045 and RFC 822, you can see that the Content-ID field and also the start part of the Content-Type field don't conform to the specifications. It is therefore not so surprising that Axis rejects the message. Maybe you should post a message to a .NET related forum about this problem. Regards, Andreas On 11 Jan 2008, at 19:00, Raghu Kasturi wrote: Hi, When I try to send the soap message using my .net Client to Axis2 service, I get the following exception: Creating an Attachments map. The content-length is6984 2008-01-11 10:39:37,184 DEBUG AxisServlet org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: FaultTo is null. Returning isReplyRedirected 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: ReplyTo is null. Returning false 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true My Soap Message is: OST /soapAdapter/services/myTestService HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2407) SOAPAction: PostRq Content-Type: Multipart/Related; boundary=5a21e1d7- c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 Content-Length: 6984 Connection: Keep-Alive Host: hostname:8090 --5a21e1d7-c13a-414f-856b-1d8db8caec7a Content-Type: text/xml Content-Transfer-Encoding: binary Content-ID: dd5584d3-dfbc-4a0a-94a9-11be8726f446 ?xml version=1.0 encoding=utf-8?soap:Envelope / soap:Envelope Please help me in this regards. Thanks, Raghu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message
Good Afternoon Andreas http://www.w3.org/TR/SOAP-attachments#CID spec calls for Content-Type: Multipart/Related; regarding cas-insensitive parameter names I do seeHowever, parameter values are case-sensitive unless otherwise specified for the specific parameter.so the label can be case-insensitivethe assigned value IS case-sensitiveMFrom: Andreas Veithen [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Friday, January 11, 2008 2:59 PM Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Raghu, If this was the origin of the problem, you should open a JIRA issue, because RFC 2045 says that All media type values, subtype values, and parameter names as defined are case-insensitive. Regards, Andreas On 11 Jan 2008, at 20:44, Raghu Kasturi wrote: Hi Andreas, Thanks for the reply. I could fix the issue, there were two problems in my SOAP message which Axis2 was not able to handle it. Content-Type: Multipart/Related; boundary=5a21e1d7-c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 One: Multipart/Related should be multipart/related (Axis2 doesn't handle it) Two: Text/xml should be text/xml (Axis2/ Axiom should handle it) Thanks, Raghu -Original Message- From: Andreas Veithen [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 12:40 PM To: axis-user@ws.apache.org Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Raghu, If you look at http://www.w3.org/TR/SOAP-attachments, RFC 2045 and RFC 822, you can see that the Content-ID field and also the start part of the Content-Type field don't conform to the specifications. It is therefore not so surprising that Axis rejects the message. Maybe you should post a message to a .NET related forum about this problem. Regards, Andreas On 11 Jan 2008, at 19:00, Raghu Kasturi wrote: Hi, When I try to send the soap message using my .net Client to Axis2 service, I get the following exception: Creating an Attachments map. The content-length is6984 2008-01-11 10:39:37,184 DEBUG AxisServlet org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: FaultTo is null. Returning isReplyRedirected 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: ReplyTo is null. Returning false 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true My Soap Message is: OST /soapAdapter/services/myTestService HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2407) SOAPAction: PostRq Content-Type: Multipart/Related; boundary=5a21e1d7- c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 Content-Length: 6984 Connection: Keep-Alive Host: hostname:8090 --5a21e1d7-c13a-414f-856b-1d8db8caec7a Content-Type: text/xml Content-Transfer-Encoding: binary Content-ID: dd5584d3-dfbc-4a0a-94a9-11be8726f446 ?xml version=1.0 encoding=utf-8?soap:Envelope / soap:Envelope Please help me in this regards. Thanks, Raghu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message
Martin, Raghu, Indeed, RFC 2045 allows Multipart/Related as in the message shown by Raghu and the SOAP specs use it explicitly as example. This makes it unlikely that this is the explanation of the problem. Whether the value of the type parameter is case sensitive or not is actually not relevant because in the SOAP message that triggered the problem it was text/xml. Raghu, are you 100% sure that you didn't change anything else? Andreas On 11 Jan 2008, at 21:31, Martin Gainty wrote: Good Afternoon Andreas http://www.w3.org/TR/SOAP-attachments#CID spec calls for Content-Type: Multipart/Related; regarding cas-insensitive parameter names I do seeHowever, parameter values are case-sensitive unless otherwise specified for the specific parameter.so the label can be case-insensitivethe assigned value IS case- sensitiveMFrom: Andreas Veithen [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Friday, January 11, 2008 2:59 PM Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Raghu, If this was the origin of the problem, you should open a JIRA issue, because RFC 2045 says that All media type values, subtype values, and parameter names as defined are case-insensitive. Regards, Andreas On 11 Jan 2008, at 20:44, Raghu Kasturi wrote: Hi Andreas, Thanks for the reply. I could fix the issue, there were two problems in my SOAP message which Axis2 was not able to handle it. Content-Type: Multipart/Related; boundary=5a21e1d7-c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 One: Multipart/Related should be multipart/related (Axis2 doesn't handle it) Two: Text/xml should be text/xml (Axis2/ Axiom should handle it) Thanks, Raghu -Original Message- From: Andreas Veithen [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 12:40 PM To: axis-user@ws.apache.org Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Raghu, If you look at http://www.w3.org/TR/SOAP-attachments, RFC 2045 and RFC 822, you can see that the Content-ID field and also the start part of the Content-Type field don't conform to the specifications. It is therefore not so surprising that Axis rejects the message. Maybe you should post a message to a .NET related forum about this problem. Regards, Andreas On 11 Jan 2008, at 19:00, Raghu Kasturi wrote: Hi, When I try to send the soap message using my .net Client to Axis2 service, I get the following exception: Creating an Attachments map. The content-length is6984 2008-01-11 10:39:37,184 DEBUG AxisServlet org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: FaultTo is null. Returning isReplyRedirected 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: ReplyTo is null. Returning false 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true My Soap Message is: OST /soapAdapter/services/myTestService HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2407) SOAPAction: PostRq Content-Type: Multipart/Related; boundary=5a21e1d7- c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 Content-Length: 6984 Connection: Keep-Alive Host: hostname:8090 --5a21e1d7-c13a-414f-856b-1d8db8caec7a Content-Type: text/xml Content-Transfer-Encoding: binary Content-ID: dd5584d3-dfbc-4a0a-94a9-11be8726f446 ?xml version=1.0 encoding=utf-8?soap:Envelope / soap:Envelope Please help me in this regards. Thanks, Raghu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message
Hi Andreas, I made change in only two files: 1. TransportUtils.java -- modified to converted Multipart/Related to multipart/related 2. BuilderUtil.java -- modified to change text/xml to text/xml I also tried printing messageBuilders Hashmap in AxisConfiguration.java which contains the key value as multipart/related where we are trying to get Multipart/Related which fails and returns null. Thanks, Raghu -Original Message- From: Andreas Veithen [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 3:44 PM To: axis-user@ws.apache.org Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Martin, Raghu, Indeed, RFC 2045 allows Multipart/Related as in the message shown by Raghu and the SOAP specs use it explicitly as example. This makes it unlikely that this is the explanation of the problem. Whether the value of the type parameter is case sensitive or not is actually not relevant because in the SOAP message that triggered the problem it was text/xml. Raghu, are you 100% sure that you didn't change anything else? Andreas On 11 Jan 2008, at 21:31, Martin Gainty wrote: Good Afternoon Andreas http://www.w3.org/TR/SOAP-attachments#CID spec calls for Content-Type: Multipart/Related; regarding cas-insensitive parameter names I do seeHowever, parameter values are case-sensitive unless otherwise specified for the specific parameter.so the label can be case-insensitivethe assigned value IS case- sensitiveMFrom: Andreas Veithen [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Friday, January 11, 2008 2:59 PM Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Raghu, If this was the origin of the problem, you should open a JIRA issue, because RFC 2045 says that All media type values, subtype values, and parameter names as defined are case-insensitive. Regards, Andreas On 11 Jan 2008, at 20:44, Raghu Kasturi wrote: Hi Andreas, Thanks for the reply. I could fix the issue, there were two problems in my SOAP message which Axis2 was not able to handle it. Content-Type: Multipart/Related; boundary=5a21e1d7-c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 One: Multipart/Related should be multipart/related (Axis2 doesn't handle it) Two: Text/xml should be text/xml (Axis2/ Axiom should handle it) Thanks, Raghu -Original Message- From: Andreas Veithen [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 12:40 PM To: axis-user@ws.apache.org Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Raghu, If you look at http://www.w3.org/TR/SOAP-attachments, RFC 2045 and RFC 822, you can see that the Content-ID field and also the start part of the Content-Type field don't conform to the specifications. It is therefore not so surprising that Axis rejects the message. Maybe you should post a message to a .NET related forum about this problem. Regards, Andreas On 11 Jan 2008, at 19:00, Raghu Kasturi wrote: Hi, When I try to send the soap message using my .net Client to Axis2 service, I get the following exception: Creating an Attachments map. The content-length is6984 2008-01-11 10:39:37,184 DEBUG AxisServlet org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: FaultTo is null. Returning isReplyRedirected 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: ReplyTo is null. Returning false 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/anonymous is Anonymous: true My Soap Message is: OST /soapAdapter/services/myTestService HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2407) SOAPAction: PostRq Content-Type: Multipart/Related; boundary=5a21e1d7- c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 Content-Length: 6984 Connection: Keep-Alive Host: hostname:8090 --5a21e1d7-c13a-414f-856b-1d8db8caec7a Content-Type: text/xml Content-Transfer-Encoding: binary Content-ID: dd5584d3-dfbc-4a0a-94a9-11be8726f446 ?xml version=1.0 encoding=utf-8?soap:Envelope / soap:Envelope Please help me in this regards. Thanks, Raghu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED
Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message
Hi Raghu, I understand now the problem with Multipart/Related. By the way there is already a bug report AXIS2-3373 that describes this issue. On the other hand, I don't understand your second point. What did you modify exactly in BuilderUtil? Andreas On 11 Jan 2008, at 23:52, Raghu Kasturi wrote: Hi Andreas, I made change in only two files: 1. TransportUtils.java -- modified to converted Multipart/Related to multipart/related 2. BuilderUtil.java -- modified to change text/xml to text/xml I also tried printing messageBuilders Hashmap in AxisConfiguration.java which contains the key value as multipart/ related where we are trying to get Multipart/Related which fails and returns null. Thanks, Raghu -Original Message- From: Andreas Veithen [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 3:44 PM To: axis-user@ws.apache.org Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Martin, Raghu, Indeed, RFC 2045 allows Multipart/Related as in the message shown by Raghu and the SOAP specs use it explicitly as example. This makes it unlikely that this is the explanation of the problem. Whether the value of the type parameter is case sensitive or not is actually not relevant because in the SOAP message that triggered the problem it was text/xml. Raghu, are you 100% sure that you didn't change anything else? Andreas On 11 Jan 2008, at 21:31, Martin Gainty wrote: Good Afternoon Andreas http://www.w3.org/TR/SOAP-attachments#CID spec calls for Content-Type: Multipart/Related; regarding cas-insensitive parameter names I do seeHowever, parameter values are case-sensitive unless otherwise specified for the specific parameter.so the label can be case-insensitivethe assigned value IS case- sensitiveMFrom: Andreas Veithen [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Friday, January 11, 2008 2:59 PM Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Raghu, If this was the origin of the problem, you should open a JIRA issue, because RFC 2045 says that All media type values, subtype values, and parameter names as defined are case-insensitive. Regards, Andreas On 11 Jan 2008, at 20:44, Raghu Kasturi wrote: Hi Andreas, Thanks for the reply. I could fix the issue, there were two problems in my SOAP message which Axis2 was not able to handle it. Content-Type: Multipart/Related; boundary=5a21e1d7-c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 One: Multipart/Related should be multipart/related (Axis2 doesn't handle it) Two: Text/xml should be text/xml (Axis2/ Axiom should handle it) Thanks, Raghu -Original Message- From: Andreas Veithen [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 12:40 PM To: axis-user@ws.apache.org Subject: Re: org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message Raghu, If you look at http://www.w3.org/TR/SOAP-attachments, RFC 2045 and RFC 822, you can see that the Content-ID field and also the start part of the Content-Type field don't conform to the specifications. It is therefore not so surprising that Axis rejects the message. Maybe you should post a message to a .NET related forum about this problem. Regards, Andreas On 11 Jan 2008, at 19:00, Raghu Kasturi wrote: Hi, When I try to send the soap message using my .net Client to Axis2 service, I get the following exception: Creating an Attachments map. The content-length is6984 2008-01-11 10:39:37,184 DEBUG AxisServlet org.apache.axis2.AxisFault: Invalid Content Type Field in the Mime Message 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: FaultTo is null. Returning isReplyRedirected 2008-01-11 10:39:37,184 DEBUG AddressingHelper [MessageContext: logID=urn:uuid:F85321AF0819DB69AE1200073177166] isReplyRedirected: ReplyTo is null. Returning false 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/ anonymous is Anonymous: true 2008-01-11 10:39:37,184 DEBUG EndpointReference hasAnonymousAddress: http://www.w3.org/2005/08/addressing/ anonymous is Anonymous: true My Soap Message is: OST /soapAdapter/services/myTestService HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2407) SOAPAction: PostRq Content-Type: Multipart/Related; boundary=5a21e1d7- c13a-414f-856b-1d8db8caec7a; type=text/xml; start=dd5584d3- dfbc-4a0a-94a9-11be8726f446 Content-Length: 6984 Connection: Keep-Alive Host: hostname:8090 --5a21e1d7-c13a-414f-856b-1d8db8caec7a Content-Type: text/xml Content-Transfer-Encoding: binary Content-ID: dd5584d3-dfbc-4a0a-94a9-11be8726f446 ?xml version=1.0 encoding=utf-8?soap:Envelope / soap:Envelope Please help me in this regards. Thanks, Raghu
