Re: Help with a simple call to http_url_post_raw

[David White <whitey.david@xxxxxxxxx>]

Hey Scott,

- I found the log file in /tmp. I swear I had looked there before and
didn't see it... at any rate I have it now. Do you see any issues in
there?

- I had received a timeout before, but that's because I had the wrong
URL, so that's the only reason I mentioned it.

- The RetLen variable is returned as *ZERO, so http_xlate is not
called to populate RetData.

- How would you encode the URL? I'm new at this :)

Thanks,

Dave

--- START LOG ---
HTTPAPI Ver 1.23 released 2008-04-24
OS/400 Ver V5R4M0

New iconv() objects set, PostRem=819. PostLoc=0. ProtRem=819. ProtLoc=0
http_persist_open(): entered
http_long_ParseURL(): entered
DNS resolver retrans: 2
DNS resolver retry  : 2
DNS resolver options: x'00000136'
DNS default domain: REDLINE.AS400.COM
DNS server found: 10.179.120.21
DNS server found: 10.179.120.20
http_persist_post(): entered
http_long_ParseURL(): entered
do_post(): entered
POST /demo/message/Ec3pl-850-OutboundOrders/type=queue&body=10015+West HTTP/1.1
Host: 10.179.120.77:8161
User-Agent: http-api/1.23
Content-Type: text/xml
Expect: 100-continue
Content-Length: 10


recvresp(): entered
HTTP/1.1 100 Continue


SetError() #13: HTTP/1.1 100 Continue
senddoc(): entered

--- END LOG ---





On Wed, Jan 19, 2011 at 11:59 AM, Scott Klement <sk@xxxxxxxxxxxxxxxx> wrote:
> Hi David,
>
> answers in-line...
>
> On 1/19/2011 11:27 AM, David White wrote:
>> Here's the code I'm running. One question I have right away is, I see
>> others have posted a log file from HTTPAPI. I haven't had any luck
>> finding this log file in my IFS. Does anyone know where I might locate
>> that log?
>
>
> By default, it's in the IFS under /tmp/httpapi_debug.txt
>
> But, you can specify an IFS pathname on the http_debug() call, so you
> can send it anywhere you like.  For example:
>
>      http_debug(*on: '/home/scott/debug.txt');
>
> Several improvements/bug fixes to the debug file support have been added
> to the current BETA version of HTTPAPI.  It might be worth a try if
> you're having problems.
>
>
>> I would love to see the log, because when I run debug through all of
>> the services in HTTPAPI (and the others), it's not fast enough to
>> meet the timeout default of 60 seconds.
>
> A timeout wouldn't return 1.  This is clearly not a timeout issue.
> (Timeout issues are rather rare in my experience, anyway...  not sure
> why you even brought it up.)
>
> Aside from the debug file, the other place to look is in your 'retdata'
> variable... what does it say there?
>
>
>>
>> 1) Do I need to encode the URL like I'm doing below?
>>
>
> The way you're encoding it is rather strange, but I don't see any reason
> why it wouldn't work?
>
> But, please understand this:   Every web page is different.  Every web
> service is different.  No two sites work the same!   Having experience
> with HTTPAPI doesn't tell me how you have to format the data for your
> particular site.  To know that, you need to be familiar with the site
> (or have documentation, or have a WSDL)
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> 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
-----------------------------------------------------------------------