Re: Headers

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

   Not sure what an "RX web service tool" is...  Probably something
   similar to SoapUI?   SoapUI is a great tool for web services, by the
   way, and it's available for free.
   The error message that you have been sent is (from the log file):
   "TypeError: can't convert NilClass into String".   That sure doesn't
   sound like it's related to the HTTP headers to me?!?!
   To me, it sounds like your XML document is wrong.
   I can't look at your XML data, since your log file appears to be
   completely screwed up.  What did you do? copy and paste it
   screen-by-screen into another file?!  Why would you do that?  The data
   is already in an ASCII file, why not just send that to us instead of
   copy/pasting (which is a lot of work, and is very error-prone) into a
   separate file?  Just send us the original!
   But, even if I could look at your XML, I couldn't help much because I
   don't know what the web service is expecting.  Show me the XML that
   your "RX web service tool" is sending, too.  Or send us the WSDL.

   On 4/26/2013 9:30 AM, Mauricio Diaz-Lapham wrote:

   Hi Scott,


   I obtained a free trial of RX web service tool. And the web service I
   am trying to consume works on that tool, but not on the HTTPAPI.

   So what I thought was, if I can find the difference between the two and
   incorporated it in the HTTPAPI, I might be able to get the HTTPAPI to
   work.


   In the RX log it shows what it passed to the server that created the
   service and the response. Here below is the log of the post.

   It has some additional headers. Now that you explained what they mean,
   I believe they should not make any difference but I thought I would try
   to add it to the HTPPAPI.


   POST /client_smart/api HTTP/1.1

   User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

   Host: 172.16.255.7:5001

   Accept: */*

   Connection: Keep-Alive

   Content-Type: text/xml; charset=utf-8
             This is from the RX tool.

   SOAPAction: "/client_smart/api/get_client"

   Content-Length: 398


   HTTP/1.1 200 OK

   Connection: close

   Date: Fri, 26 Apr 2013 13:15:39 GMT


   I talked to the vendor that created the service and they were able to
   capture what we send to them. The first log shows how a successful call
   looks like and the second is the one is the one I sent using HTPPAPI
   and it failed. I am also including the log from the HTPPAPI and my
   code. I think its something on their server, but what is a mystery is
   why some tools work and others don't.

   Thanks for your help.


   Here the TCP Stream on a successful call. It sends a POST request.

   [1]cid:image002.jpg@01CE41B3.22275EC0


   Here's the TCP Stream on Mauricio's  failing call. Note no POST
   request.

   [2]cid:image006.jpg@01CE41B3.22275EC0


-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
[3]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------

References

   1. cid:image002.jpg@01CE41B3.22275EC0
   2. cid:image006.jpg@01CE41B3.22275EC0
   3. http://www.scottklement.com/mailman/listinfo/ftpapi

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------