Well, HttpSecureSocket is smart enough to set the secure property
based upon the url
so you can just say
https = new HTTPSecureSocket()
msgbox https.get("http://foo.com/";)
and it'll know it use http
Our application uses HTTPSecureSockets exclusively for communication
and doesn't have any problems with either HTTP or HTTPS urls.
You should be able to just do a drop in replacement (change the super
and make no other changes) with httpsecuresocket and it should
perform the same as httpsocket did (well as far as http urls are
concerned).
The one issue that will cause you grief is if you have to navigate a
http proxy. HTTPSecureSocket does not work with proxies (either in
secure or non secure mode).
-jason
On Apr 7, 2006, at 2:25 AM, Guyren Howe wrote:
On Apr 7, 2006, at 1:56 AM, Guyren Howe wrote:
I create a HTTPSocket subclass, I ask it to get an address, it
works fine.
I change its super to HTTPSecureSocket, I add the following
constructor:
Me.Secure = False
Super.Constructor
and I ask it to get the same address, it eventually fails with a
103 error (which the TCPSocket docs say is a DNS failure).
I can't find a bug report on this. Anyone have any advice?
Oh, and this is 2K6r1 on OS X.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
-jason
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
