Dayum, have you got a lot to catch up on! ;)
On 27/12/2011, at 3:52 PM, st...@forerunners.org wrote: > > What ever happened to this list server? is this group still > together...been a few years. > > Steve > > >> Steve, >> >> I would suggest that you try a different tool, like curl, to generate the >> web service request, and see if you can get the server to accept your >> request. >> >> Also, Since building the message in witango requires hacks, (like setting >> the useragent to add the SOAPAction header) I started using a different >> method for communicating with one of our primary soap based webservices. >> >> Here is a bash script that uses curl to actually send the request. You >> invoke it with an external action in witango. I know that chances that >> you're running witango in a linux environment are pretty slim, but you >> might >> be able to learn from it. >> >> CT, SOAPACTION, DATA and URL are all environemnt varaibles passed in from >> witango. >> >> #!/bin/bash >>> >>> /usr/bin/curl -k -s -m 100 --connect-timeout 91 \ >>> --header "Content-type: $CT" \ >>> --header "SOAPAction: \"$SOAPACTION\"" \ >>> --DATA "$DATA" \ >>> "$URL" >>> >> >>> # Check the status code of the last command to execute "curl" >>> # if it's not 0 (OK) then echo that error >>> # if it is zero, the output of curl will simply be >>> # the response to the message >>> ce=$? >>> if [ $ce -ne 0 ] >>> then >>> echo "CURL-ERROR:$ce" >>> fi >>> >> >> Using this script was nice because it also allowed us to be particular >> about >> how long we'll wait for the webservice to responsd (the -m and >> --connect-timeout parameters) >> >> If we continued to use @url for those connections, we were at the mercy of >> querytimeout, which isn't a good thing if you have a lot of web service >> requests, that start to timeout because the remote server goes offline. >> >> /John >> >> On Tue, Dec 30, 2008 at 11:29 PM, Fogelson, Steve >> <stevefogel...@askics.net>wrote: >> >>> I'm back. I have reduced my code to the following. John's code, Ben's >>> suggestion and Witango docs. I get this response: "Server did not >>> recognize the value of HTTP Header SOAPAction: :SOAPAction." >>> >>> >>> >>> Any ideas? >>> >>> >>> >>> Steve >>> >>> >>> >>> <@assign request$urllocation " >>> http://apiv2.gunbroker.com/AuctionService.asmx"* encoding=*"none"> >>> >>> <@assign request$SOAPAction "GunBrokerAPI_V2/Login"> >>> >>> >>> >>> <@assign request$SOAPPayload ' >>> >>> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soap=" >>> http://schemas.xmlsoap.org/soap/envelope/";> >>> >>> <soap:Body> >>> >>> <Login xmlns="GunBrokerAPI_V2"> >>> >>> <UserName>*@@*request$UserName</UserName>** >>> >>> <Password>*@@*request$Password</Password>** >>> >>> <DevKey>*@@*request$DevKey</DevKey>** >>> >>> <AppKey>*@@*request$AppKey</AppKey>** >>> >>> </Login> >>> >>> </soap:Body> >>> >>> </soap:Envelope> >>> >>> '>** >>> >>> >>> >>> <@assign request$SOAPResponse " >>> >>> <@url** >>> >>> *location=*'*@@*request$urllocation'** >>> >>> *useragent=*'Witango <@version> <@platform><@crlf>Content-type: text/xml >>> <@crlf>SOAPAction: "*@@*request:SOAPAction"'** >>> >>> postargs='<?xml version=<@sq>1.0<@sq> encoding=<@sq>utf-8<@sq>?> >>> <@crlf><@crlf><@var request$SOAPPayload* encoding=*none>'** >>> >>>> ">** >>> >>> * * >>> >>> <pre>** >>> >>> <@var request$SOAPResponse* encoding=*"html"> >>> >>> </pre>** >>> >>> >>> >>> >>> ************************************************************************************ >>> >>> I am getting the following response: >>> >>> >>> >>> <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap=" >>> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi=" >>> http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd=" >>> http://www.w3.org/2001/XMLSchema";><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Server >>> did not recognize the value of HTTP Header SOAPAction: >>> :SOAPAction.</faultstring><detail >>> /></soap:Fault></soap:Body></soap:Envelope> >>> >>> >>> >>> ***************************************************** >>> >>> GunBroker.com provides the following example >>> >>> >>> >>> POST /AuctionService.asmx HTTP/1.1 >>> >>> Host: apiv2.gunbroker.com >>> >>> Content-Type: text/xml; charset=utf-8 >>> >>> Content-Length: length >>> >>> SOAPAction: "GunBrokerAPI_V2/Login" >>> >>> >>> >>> <?xml version="1.0" encoding="utf-8"?> >>> >>> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >>> >>> <soap:Body> >>> >>> <Login xmlns="GunBrokerAPI_V2"> >>> >>> <UserName>string</UserName> >>> >>> <Password>string</Password> >>> >>> <DevKey>string</DevKey> >>> >>> <AppKey>string</AppKey> >>> >>> </Login> >>> >>> </soap:Body> >>> >>> </soap:Envelope> >>> >>> >>> >>> ________________________________________________________________________ >>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>> >>> ________________________________________________________________________ >>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>> >>> ________________________________________________________________________ >>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>> >>> >> >> >> -- >> /John >> >> ________________________________________________________________________ >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > > > ---------------------------------------- > > To unsubscribe from this list, please send an email to lists...@witango.com > with "unsubscribe witango-talk" in the body. > ---------------------------------------- To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body.
