Uploaded image for project: 'EVSClient'
  1. EVSClient
  2. EVSCLT-340

Content Analyzer should recognize MTOM even if we do not start by the MTOM section

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: High
    • Resolution: Cannot Reproduce
    • Affects Version/s: 4.4.0
    • Fix Version/s: 5.1.5
    • Component/s: Content Analyzer
    • Labels:
      None
    • Sprint:
      Sprint 37, 2017 - S6
    • Account:
      IHE Europe (IHE2012)

      Description

      Please look at the following exemple :
      http://gazelle.ihe.net/EVSClient/messageContentAnalyzerDetailedResult.seam?&oid=1.3.6.1.4.1.12559.11.1.2.1.4.67632
      As you can see the MTOM section is provided after the HTTP Header information :

      POST /tf6/services/xdsrepositoryb HTTP/1.1
      Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_566EAD10FEBB55C5A61257193478449; type="application/xop+xml"; start="<0.urn:uuid:566EAD10FEBB55C5A61257193478450@apache.org>"; start-info="application/soap+xml"; action="urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b"
      User-Agent: Axis2
      Host: localhost:5000

      --MIMEBoundaryurn_uuid_566EAD10FEBB55C5A61257193478449
      Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml"
      Content-Transfer-Encoding: binary
      Content-ID: <0.urn:uuid:566EAD10FEBB55C5A61257193478450@apache.org>
      ....

      - Detect the MTOM Mime Boundary even if we do not start by it

        BigPicture - Work Breakdown Structure

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                gthomazon Guillaume Thomazon
                Reporter:
                epoiseau Eric Poiseau
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  BigPicture - Skills

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Time Tracking

                      Estimated:
                      Original Estimate - 1 day, 2 hours
                      1d 2h
                      Remaining:
                      Remaining Estimate - 0 minutes
                      0m
                      Logged:
                      Time Spent - 2 hours Time Not Required
                      2h

                        Potential Duplicates