[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (no subject)
Hi Harry,
Please make sure you're running the latest version of HTTPAPI. There
were some bugs related to this that were fixed last year. You should be
able to upgrade without changing (or even compiling or binding) any of
your existing code.
If that still doesn't help, then I need more information about the problem.
I don't understand your fix -- it doesn't make any sense to me. The only
reason that calling RespProc more than once would help is if you're
receiving multiple responses from the server (which would violate the
HTTP 1.1 standard). A debug log might tell me more -- but see if
upgrading to the latest version helps, first. I don't want to spend
too much time on this if the problem has already been fixed!
Harry Williams wrote:
> Scott
> I hope this is better.
>
> I was asking about the 100 Continue message tryng to understand what it
> was doing. In the process of testing the 100 message, I found that if I
> put a look in
>
> In the DO_POST routine, I added the following. It is a little poor
> programming, but it just shows that I put the RespProc in to a loop
> while the return code was 0. I was reading some of the posts, and it
> appeared that the 100 continue has been a pain. I didn't know if this
> would help you with the DO_POST routine or not. But it seemed to solve
> my problem.
>
> Nestrest Tag
> eval rc = RespProc(peComm: wwRespChain:
> %size(wwRespChain): petimeout: *ON )
> if rc = 0
> add 1 cnt 5 0
> add 1 petimeout
> if cnt < 10
> goto Nestrest
> endif
> endif
> if rc < 1
> return rc
> endif
>
>
>
> I tried changing the PEtimeout, and it didn't seem to work, so I tried
> this. If this helps, I was offering it up for a solution.
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------