Re: Feature: TCPconnect via SSL
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 25336
interpreted = N
texte = The answer is probably no, because of the complicated nature of SSL. It is not really what TCPconnect was intended to do. If you don't want to pay for WebCat/WebMerchant and want to brew your own CC authorization scheme, you're in for a world of hurt.See the following link if you are really curious about SSL:http://developer.netscape.com/docs/manuals/security/sslin/contents.htmHTHJohn Peacock____________________Reply Separator____________________ Subject: Feature: TCPconnect via SSL Author:
Date: 12/9/99 12:19 PMAny chance that the TCPconnect context will be able to communicate via SSL in the next version?I know that TCPconnect can communicate on port 443, but I need to be able to not only communicate on port 443, but to send and receive via SSL on that port.Thanks, ___Joe____________________________________________________ Joseph D'Andrea JoeDan@West21.com WEST21.com Internet services for the 21st Century http://www.west21.com/ _________________________________________________############################################################# This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
The answer is probably no, because of the complicated nature of SSL. It is not really what TCPconnect was intended to do. If you don't want to pay for WebCat/WebMerchant and want to brew your own CC authorization scheme, you're in for a world of hurt.See the following link if you are really curious about SSL:http://developer.netscape.com/docs/manuals/security/sslin/contents.htmHTHJohn Peacock____________________Reply Separator____________________ Subject: Feature: TCPconnect via SSL Author: Date: 12/9/99 12:19 PMAny chance that the TCPconnect context will be able to communicate via SSL in the next version?I know that TCPconnect can communicate on port 443, but I need to be able to not only communicate on port 443, but to send and receive via SSL on that port.Thanks, ___Joe____________________________________________________ Joseph D'Andrea JoeDan@West21.com WEST21.com Internet services for the 21st Century http://www.west21.com/ _________________________________________________############################################################# This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
jpeacock@univpress.com
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WebDNA Promo Sound Bite (2003)
Help name our technology! I found it (1997)
Newbie problem blah blah blah (1997)
Okay, I give up... (1999)
emailer (1997)
WebCat2 several catalogs? (1997)
(2000)
Max Record length restated as maybe bug (1997)
weird user / authenticate happenings (2003)
Firewalls - What's Good? (1999)
[WebDNA] Looking for Govinda (2011)
Mass Mail (2000)
WebCat2b12 - nesting [tags] (1997)
webmerchant/ Mac Auth. and CC refunds (1998)
multiple selected Checkboxes (1998)
PSC recommends what date format yr 2000??? (1997)
getting images' width/height (1998)
WebCat2: multiple currency support (1997)
upload pictures any solution (1999)
docs for WebCatalog2 (1997)