Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-806

@ symbol in the content-id is converted to %40. The receiving web server is not able to handle it


    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Works as Designed
    • Affects Version/s: 1.5.6
    • Fix Version/s: 2.1.2
    • Component/s: XML
    • Labels:



      Spring ws version :1.5.6
      Marshaller: Jaxb2Marshaller

      Problem description: I am sending a series of Spring MTOM attachments to a webservice.In the Content-Id inside the "XOP" tag in the request XML there is a special character '@' which is encoded as % + ASCII hexadecimal
      The web service provider is not able to handle this.

      Please refer the following XML for issue.

      • <<ns6:BinaryBase64Object>
        <<xop:Include href="cid:be434728-da9e-4b88-858f-065cc11074a0%40niem.gov" xmlns:xop="http://www.w3.org/2004/08/xop/include" />

      — ------=_Part_4_1104626135.1351225350567
      Content-Type: application/octet-stream
      Content-Transfer-Encoding: binary
      Content-Id: <[email protected]>

      My question is as follows
      1. Is this an issue or is that a standard process of encoding the Content-Id
      2. Can I stop encoding from happening.
      3. How is the Content-Id in Spring generated. How can i stop using Spring from using @niem.gov in the Content-Id.
      4. In which jar file is the code for Content-Id.
      5. Should this be handled at the service provider or consumer side.
      6. How can i get around this problem?


        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        33d 8h 47m 1 Arjen Poutsma 03/Dec/12 4:49 AM
        In Progress In Progress Resolved Resolved
        1h 6m 1 Arjen Poutsma 03/Dec/12 5:56 AM


          • Assignee:
            arjen.poutsma Arjen Poutsma
            jashandeep Jashandeep Singh Dhillon
          • Votes:
            0 Vote for this issue
            1 Start watching this issue


            • Created:

              Time Tracking

              Original Estimate - Not Specified
              Not Specified
              Remaining Estimate - Not Specified
              Not Specified
              Time Spent - 1h 7m
              1h 7m