[AOLSERVER] TLS package issue

[aT]

Hi ,

We are using the TLS package to call a certain HTTPs API, we do usually
import the package using "package require" command then doing a normal
"::http::register https 443 ::tls::socket"

Sometimes a strange error just appear saying that "invalid ::tls:socket
command".

Am assuming that the issue is happening due to a failure while importing
the TLS package and its random.. may be this is happening because the
package is already imported and am trying to import it again? or because
of an open sockets somewhere that should be closed? is it a bug in AOL?

We are using Aolserver 4.0.10 . TLS version is 1.6 Its a 64bit linux
environment ,

Has any one encountered same using TLS .

Atif

--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <list...@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.

[aT]

Hi ,

We are using the TLS package to call a certain HTTPs API, we do usually
import the package using "package require" command then doing a normal
"::http::register https 443 ::tls::socket"

Sometimes a strange error just appear saying that "invalid ::tls:socket
command".

Am assuming that the issue is happening due to a failure while importing
the TLS package and its random.. may be this is happening because the
package is already imported and am trying to import it again? or because
of an open sockets somewhere that should be closed? is it a bug in AOL?

We are using Aolserver 4.0.10 . TLS version is 1.6 Its a 64bit Linux

[Fenton, Brian]

Hi Atif

I can confirm that we're running TLS 1.6 with AOLserver 4.5.1 on Suse 9.4 64 bit and I've never seen this problem. However, we haven't tested it under heavy loads yet.

hope this helps
Brian Fenton

________________________________________
From: AOLserver Discussion [AOLS...@LISTSERV.AOL.COM] On Behalf Of aT [atif...@GMAIL.COM]
Sent: 06 December 2010 11:19
To: AOLS...@LISTSERV.AOL.COM
Subject: [AOLSERVER] TLS package issue

[Jeff Hobbs]

On 06/12/2010 3:14 AM, aT wrote:
> We are using the TLS package to call a certain HTTPs API, we do usually
> import the package using "package require" command then doing a normal
> "::http::register https 443 ::tls::socket"
>
> Sometimes a strange error just appear saying that "invalid ::tls:socket
> command".

Is this a copy & paste direct? If so, tls::socket has 2 :s, the above
shows only one, so it would be a correct complaint. Otherwise just make
sure there is a reference to 'package require tls' before tls is used.

> Am assuming that the issue is happening due to a failure while importing
> the TLS package and its random.. may be this is happening because the
> package is already imported and am trying to import it again? or because
> of an open sockets somewhere that should be closed? is it a bug in AOL?
>
> We are using Aolserver 4.0.10 . TLS version is 1.6 Its a 64bit linux
> environment ,
>
> Has any one encountered same using TLS .

BTW, everyone should be using 1.6.1 because it fixed a mem leak on each
tls::status call.

Jeff

[Michael A. Cleverly]

On Mon, Dec 6, 2010 at 10:18 AM, Jeff Hobbs <je...@activestate.com> wrote:

> BTW, everyone should be using 1.6.1 because it fixed a mem leak on each
> tls::status call.

I only see "1.6" at http://sourceforge.net/projects/tls/files/tls/
(released on 2008-03-24). Where is the best place to grab 1.6.1?

Michael

[Jeff Hobbs]

On 06/12/2010 1:14 PM, Michael A. Cleverly wrote:
> On Mon, Dec 6, 2010 at 10:18 AM, Jeff Hobbs<je...@activestate.com> wrote:
>
>> BTW, everyone should be using 1.6.1 because it fixed a mem leak on each
>> tls::status call.
>
> I only see "1.6" at http://sourceforge.net/projects/tls/files/tls/
> (released on 2008-03-24). Where is the best place to grab 1.6.1?

Ah, lazy me. It's tagged in cvs but has never had the dist placed on SF
Files.

Jeff

[aT]

Thanks for the response ,

I am using the updated 1.6.1 and still getting this error and yes
"package require tls " is mentioned before tls is used .

Problem still persist .

[Bernhard van Woerden]

An alternative package is TclCurl which works well for us inside AOLserver.

[aT]

Thanks Bernhard ,

Yes we are trying TclCurl and so far it seems to be working fine .