Forum Discussion

depeche's avatar
depeche
Contributor
16 years ago

HTTP/1.1 400 Bad Request:<wsa:ProblemHeaderQName>wsa:Action</wsa:ProblemHeaderQN

Hi,

I have a problem with SoapUI, I use a wsdl which is tested using xdstest tool other than SoapUi, it worked fine, but when I tried to use SOAP UI
I got following error (captured at TcpMon):

HTTP/1.1 400 Bad Request
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml; action="http://www.w3.org/2005/08/addressing/fault";charset=UTF-8
Transfer-Encoding: chunked
Date: Wed, 09 Dec 2009 11:18:19 GMT
Connection: close

3a5

   

      http://www.w3.org/2005/08/addressing/fault
      urn:uuid:4772851B96CCD2378E1260256352332
   

   
     
         
            soapenv:Sender
           
               wsa:InvalidAddressingHeader
               
                  wsa:ActionMismatch
               

           

         

         
            A header representing a Message Addressing Property is not valid and the message cannot be processed
         

         
            wsa:Action
         

     

   

0

Basically what i see through my request is that the action is empty. I tried setting the value as "urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b" through Headers panel as well as through WS-A Action, but action value remains as it is (i.e. action=\"\"";).

Note: I am attaching a text document in the request , i.e. why i made Enable MTOM & Force MTOM as true.

WSDL location: http://ihexds.nist.gov:9080/tf6/service ... toryb?wsdl
here is my request from soapUI (RAW view)

POST http://127.0.0.1:9080/tf6/services/xdsrepositoryb HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: multipart/related; type="application/xop+xml"; start=""; start-info="application/soap+xml; action=\"\""; boundary="----=_Part_19_21755481.1260357207171"
MIME-Version: 1.0
User-Agent: Jakarta Commons-HttpClient/3.1
Host: 127.0.0.1:9080
Content-Length: 13109


------=_Part_19_21755481.1260357207171
Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml; action=\"ProvideAndRegisterDocumentSetRequest\""
Content-Transfer-Encoding: 8bit
Content-ID:



http://127.0.0.1:9080/tf6/services/xdsrepositoryb
urn:uuid:4772851B96CCD2378E1260256352332
urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b








20051224






en-us






200412230800






200412230801






89765a87b^^^&3.4.5&ISO






PID-3|pid1^^^&1.2.3&ISO
PID-5|Doe^John^^^
PID-7|19560527
PID-8|M
PID-11|100 Main St^^Metropolis^Il^44130^USA
















^Smitty^Gerald^^^






Cleveland Clinic
Parma Community







Attending






Orthopedic












^Dopplemeyer^Sherry^^^






Cleveland Clinic
Berea Community







Primary Surgon






Orthopedic












Connect-a-thon classCodes














Connect-a-thon confidentialityCodes














Connect-a-thon formatCodes














Connect-a-thon healthcareFacilityTypeCodes














Connect-a-thon practiceSettingCodes














LOINC





























20041225235050















^Dopplemeyer^Sherry^^^






Cleveland Clinic
Berea Community







Primary Surgon






Orthopedic








Connect-a-thon contentTypeCodes





































Original











------=_Part_19_21755481.1260357207171
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

This is my document.

It is great!


------=_Part_19_21755481.1260357207171--





The valid request prepared by xdstest tool which went through is as follows:

[ValidRequest.txt in the attachment]


Thank you very much for your help.

Thanks,
depeche
  • Hi depeche,

    thanks for reporting, I've fixes this so your request works better (if you enable ws-a and the corresponding options in the ws-a panel).. I'll create a build for you to try out right away.. ok?

    regards!

    /Ole
    eviware.com
  • Hi Ole,
          After enabling ws-a and the corresponding options in the ws-a panel, i still get the same error. If you had done fixes, please let me know from where i can get it?

    Thanks,
      depeche
  • Hi
        Thanks for looking into the issue. Its been solved. Gr8! work guys 

    Thanks & regards,
    depeche