[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HTTPIPA QUESTION



Hi Rick,

There have been numerous bug fixes to HTTPAPI since version 1.9 was released over 2 years ago. Please download version 1.12 and see if it solves the problem.

If not, please tell me how to reproduce the problem (with version 1.12) so that I can try to see what's going wrong.

---
Scott Klement  http://www.scottklement.com

On Fri, 2 Dec 2005, Rick Ms wrote:

Sender: Rick Ms <rickmsusa@xxxxxxxxx>


I'm having a problem receiving a response from a web server. Any help and/or suggestions would be appreciated tremendously. Here is a short description of what is happening.

 I integrated Scott's HTTPAPI 1.9 to send an HTTP
Post request to my company's business partner Web
Server. Everything works nice and consistently when
sending the request to the partner's integration URL.
However, sending the request to their production URL
does not work. Supposedly, both environments should be
identical..!

I have been able to verify the following:
a) The socket connection is being established
consistently with their production host/URL
b) The problem occurs after sending the initial
request line. For some reason I get the "100-continue"
from their integration URL, but I don't get this
status line from their production URL. I changed the
code to increase the wait time from 0.5 to 10.5
seconds (thinking that it would help). It still didn't
work.

The HTTPAPI is smart enough to ignore the absence of
the ?100-continue? message and send the body of the
request anyway. However, by the time the HTTPAPI
attempts to receive the next response the socket has
already been shut down from the server site (jugging
from the return code (zero) on the RECV API.

Can anyone give me an idea on how to overcome this
situation? The sooner the better :) I don't want to go
bold before my wedding..!