RE: CommSSL_Read timeout

["Barry Shrum" <barry@xxxxxxxxxxxxxxx>]

Scott,

Thanks, I'll start the upgrade.

Barry

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Scott Klement
Sent: Tuesday, September 04, 2007 12:51 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: CommSSL_Read timeout


Hi Barry,

The "CommSSL_read timeout" message is a normal, expected message -- and 
has nothing to do with your problem.

That log file says that the issue is that the page has "moved 
temporarily" (which usually means that it's trying to redirect you to a 
different URL, in this case, https://www.someurl.com)

The site expects you to get that URL (which can be retrieved by calling 
HTTP_redir_loc() API in HTTPAPI) and then try performing a GET request 
on that site.

The web server is also sending you cookies, which should be re-submitted 
to the new site.  However, since you're running a very old version of 
HTTPAPI, you'll have to do the cookie processing manually, HTTPAPI 
didn't understand cookies until version 1.16.

You may want to start by updating HTTPAPI.


Barry Shrum wrote:
> Two days ago I started getting a CommSSL_Read: timeout! error. We
> have been using HTTPAPI for several months in a development project
> without having this problem.  I included parts of the log file.  I
> changed the trading partner information as per their confidentiality
> requirements.

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------

-- 
This message has been scanned and appears to be clean.

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------