Craig, Thursday, April 21, 2005, 4:28:33 PM, you wrote:
CB> David, CB> if you are doing a POST, shouldn't this bit: >> API=CustomsCN22&XM >> L=<CustomsCP72V2Request USERID=91919191919 >> PASSWORD=1919191919191><Option/><From >>FirstName>John</FromFirstName><FromLastName>Smith >></FromLastName><FromFirm>XYZ Co >> rporation</FromFirm><FromAddress1>Suite CB> A</FromAddress1><FromAddress2>1234 Etail >> er Dr.</FromAddress2><FromUrbanization/><FromCity>Los CB> Angeles</FromCity><FromSta >> te>CA</FromState><FromZip5>90052</FromZip5> ... </CustomsCP72V2Request> CB> be in the body rather than the url? if you are not sending any content CB> in the request (and all the parameters are in the url) you should CB> probably use GET. I had tried both GET and POST. In both cases the url never got encoded .. as i thought the manuals say CB> Off the top of my head maybe you need to: CB> addrequestparamter to add API with a value of CustomsCN22 CB> then to add XML with a value containing your XML string. so as i *thought* addrequestparameter is for POST and used to build the 'parameter'/'value' pairs .. CB> Either way, you would think the request process would check that the url CB> was correctly encoded. yes .. since there is no URLENCODE/URLDECODE commands .. yes you would think it would do this. Thanks i will keep playing with this ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
