Re: httpapi https_connect() problem

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Sender: Scott Klement <sk@xxxxxxxxxxxxxxxx>

Hi Ian,

>
> We are connecting via SSL, so the procedure is https_connect()
>

Please upgrade to the current version of httpapi.  In that version, the
procedure will be called CommSSL_Connect().

> When we connect to the remote server over an Internet connection (AS/400 -
> LAN router - Internet) everything works fine.
> When we connect using dial-up (modem - telephone line) using TCPPTP profiles
> we get an error:
> "invalid argument" - this is at the second https_connect checking whether
> the connection worked.

This might be fixed in 1.10, since I re-wrote almost all of the networking
stuff.

If it is not fixed in 1.10, you might try leaving the socket in blocking
mode to see if that helps.

Using blocking mode will prevent HTTPAPI from being able to check for
sockets timing out, so you could potentially get stuck "forever" if you
disable non-blocking.  But, it might at least narrow down the problem.

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------