1 2 Previous Next 16 Replies Latest reply on Mar 31, 2005 8:15 PM by Jason Greene

    Malformed Content-Id in SOAP Attachment Response?

    Greg Crider Newbie

      I have a JSE web service that returns a DataHandler. The client side throws an exception saying it can't find the Content-Id specified in the SOAP response. Using ethereal, I captured the entire response, and can clearly see the attachment, however, there does appear to be a problem with the Content-Id in the MIME portion. Here is the SOAP response I get back from JBoss AS 4.0.1:


      HTTP/1.1 200 OK
      X-Powered-By: Servlet 2.4; Tomcat-5.0.28/JBoss-4.0.1 (build: CVSTag=JBoss_4_0_1 date=200412230944)
      Content-Type: multipart/related; type="text/xml"; start="<AEF4379B67A42412258E335FA85EE750>"; boundary="----=_Part_13_24567153.1106763566149"
      Transfer-Encoding: chunked
      Date: Wed, 26 Jan 2005 18:19:26 GMT
      Server: Apache-Coyote/1.1

      2cb

      ------=_Part_13_24567153.1106763566149
      Content-Type: text/xml; charset=UTF-8
      Content-Transfer-Encoding: binary
      Content-Id: <AEF4379B67A42412258E335FA85EE750>

      <?xml version="1.0" encoding="UTF-8"?>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
      <ns1:downloadResponse xmlns:ns1="urn:server.transport.rbu.edc.com/ServerFile">
      <result href="cid:A9FCB00186FA6E4FFC4DB12F3B36CAFB" xmlns:ns2="http://java.sun.com/jax-rpc-ri/internal"/>
      </ns1:downloadResponse>
      </soapenv:Body>
      </soapenv:Envelope>
      2000

      ------=_Part_13_24567153.1106763566149
      Content-Type: text/html
      Content-Transfer-Encoding: binary
      Content-Id: <A9FCB00186FA6E4FFC4DB12F3B36CAFB>

      .... attached file removed by poster for clarity ...

      ------=_Part_13_24567153.1106763566149--

      0

      In the SOAP envelope, you can see "cid:A9FCB00186FA6E4FFC4DB12F3B36CAFB", but in the MIME portion where the attachment lives, the Content-Id is wrapped with < and >. I think this is causing the exception in my client.

      Any thoughts?

        1 2 Previous Next