RE: Success HttpApi on V4R3

["Art Tostaine, Jr." <artjr@xxxxxxxxxxx>]

Sender: "Art Tostaine, Jr." <artjr@xxxxxxxxxxx>

Scott:

Thanks for the ideas.  I will probably try to hijack the API's.

The Post is supposed to call a "program" called Populate on their system, and I am supposed to invoke method "varPayload"

They want me to send this URL:

http://xxx.xxx.xxx.xxx/Integration/Integration.asmx/Populate

and I have this in my STMF:

"varPayload=<?xml version="1.0" encoding="utf-8" ?>
<RouteRequest xmlns="http://206.188.52.206/Integration/RoutePopulateRequest.xsd";>
 <Partner>
  <CustomerID>Gilbert</CustomerID>
  <CustomerUID>Art</CustomerUID>
  <CustomerPWD>Art</CustomerPWD>
  <Version>1.0</Version>
  <Type>GIS</Type>
  <Source>Gilbert</Source>

etc, etc, etc.

_________________
Art Tostaine, Jr.
CCA, Inc.
Jackson, NJ 08527 

> -----Original Message-----
> From: owner-ftpapi@xxxxxxxxxxxxx [mailto:owner-ftpapi@xxxxxxxxxxxxx]On
> Behalf Of Scott Klement
> Sent: Wednesday, October 30, 2002 5:19 PM
> To: ftpapi@xxxxxxxxxxxxx
> Subject: Re: Success HttpApi on V4R3
> 
> 
> Sender: Scott Klement <sk@xxxxxxxxxxxxxxxx>
> 
> 
> Based on what you've said in past messages, I'm guessing that they don't
> just want plain XML, but they actually want it encoded to fit into
> a web form, in a variable called varPayload.
> 
> That would be a strange thing to do, IMHO, but that may be the piece of
> the puzzle that you're missing...
> 
> as for seeing exactly what's sent out, there's several ways...
> 
> 1) Use a "debugging proxy", a simple sockets program that reads your
>       data and copies it to the remote HTTP server as well as to a file
>       so you can see what's being sent/received.   I use this quite often.
>       It's particularly helpful to run both HTTPAPI, and Internet Explorer
>       or Mozilla thru the same proxy, so you can compare the diffs.
> 
> 2) Use a network sniffer.  Same principle as #1, but without the custom
>       programming.   May not work, depending on how your network is
>       configured.  Also may violate your company's security policies,
>       I don't know.
> 
> 3) Add code to HTTPAPI to show you what's going on.  In particular,
>       the data in SendReq(), RecvResp(),RecvDoc() and RecvChunk()
>       could have code added to save the sent/received data to a
>       file or something.
> 
> 4) You could "hijack" the send() and recv() APIs (i.e. replace them
>       with your own procedures) and use that to debug from...
> 
> Wow, I'm full of ideas today.  :)
> 
> 
> On Wed, 30 Oct 2002, Art Tostaine, Jr. wrote:
> >
> > Now, when I post, I receive an internal server error.
> >
> > I'm probably sending them something wrong.
> >
> > Is there a way to trace somehow EXACTLY what is being sent out?
> >
> > Thanks.
> 
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubsribe from the list send mail
> to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
> -----------------------------------------------------------------------
> 
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------