O.K. it isn't so weird ...
It appears that there are two problems.
1) I was mistaken about the Secure property. I guess the socket isn't
smart enough to set itself.
2) The HTTPSecureSocket is also a bit stupid about the port
so if you do
secure = false
defaultport = 80
get("http://relevantlogic.com";)
Life will be good.
Alternately:
secure = false
get("http://relevantlogic.com:80";)
would also work.
Google worked because the socket ignored the http part and attempted
to connect (actually did) via https on port 443.
I suppose there is an opportunity to file a feature request to make
httpsecuresocket a little smarter about the handling of urls
for http set secure to false and defaultport to 80 and for https
secure = true and defaultport = 443
It is smart enough to pick up nonstandard ports from the URL however.
so, it is not a bug per-se but rather a less than complete
implementation.
-jason
On Apr 7, 2006, at 2:58 PM, Guyren Howe wrote:
This gets weirder. Success or failure appears to depend on which
website you're trying to fetch. www.google.com works.
relevantlogic.com doesn't.
_______________________________________________
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>
