Well, I tried curl -v but it didn't display any information until the
transaction was completed, it seemed.

Here's some additional info:
- The server that is having trouble is inside a firewall, I believe. But I'm
thinking that if data comes back AT ALL, then the firewall can't be the
problem. It should stop data completely, right?

- I copied the application to an entirely different server that had nothing
to do with the current company's server, and the transactions came back
within 4 seconds every time. We tried another POST method (via Windows
desktop/HTML page) instead of cURL and it came back within 4 seconds every
time as well. I am not sure if that computer is behind the firewall or not.

- Every once in a while, I will get a transaction back extremely quickly.

- There isn't a lot of network load on the server. Nowhere near enough to
warrant this type of slowness.

Any other ideas?

- Jonathan

-----Original Message-----
From: Daniel Stenberg [mailto:daniel_at_haxx.se]
Sent: Friday, October 19, 2001 1:37 AM
To: Curl Mailinglist
Subject: Re: Hangs every other transaction

On Thu, 18 Oct 2001, Jonathan Hilgeman wrote:

> I use cURL + SSL to connect to a gateway and I send transactions to the
> gateway and receive info back for parsing. However, I've been having a
> lot of problems with cURL simply hanging. Finally, I reduced my tests
> down to a simple command line test:
>
> curl https://gateway.location.url
>
> And the first thing I get back is the appropriate error message from the
> gateway saying invalid configuration, which is what SHOULD happen. This
> happens within 1-2 seconds. Then, I hit the up arrow to repeat the exact
> same command, and it just hangs there until I hit CTRL+C to break out.
> This only happens with a certain gateway. All other https and http URLs
> seem to work fine. Any ideas anyone?

It certainly sounds as if that particular gateway is the one to blame for
this.

You could use curl -v to view the protocol interaction to see if that offers
any hints and you could try a network sniffer to see if there's any data at
all sent from the 'gateway'.

You could also consider talking to the admins of that gateway to get to know
if they can see anything odd in their log files or similar.

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/