Howdi, you don't need any standards document to prove that it is true, you just need to consider basic http/s transfer protocols. consider any http session - it starts when the user clicks a button or link or enters a url in the location box. after that, if it's http, the browser opens a normal connection to the server on port 80, if it's https, then the browser opens an encrypted connection to the server on port 443. the encryption process happens way up in the communications structure - right after it comes out of the application and into the transport (i recommend googling for "ISO/OSI Network Model", you will see that encryption process has it's own network layer)
simple as that :-) it's always been that way - ever since https was even invented. > Additionally, I would assume this was not always the case? > Because I know > I have been educated to believe that a FORM is not secure > unless it was rendered through a HTTPS call. depending on how that statement is interpreted, it could well be true. if the form was not rendered through https, then the form content is not secure. says nothing about what happens to the data that is submitted from that form. cheers! Mike. +----------------------------------------------------+ | VeriPay mPOS - Anywhere, Anytime | | Puts money in your bank while you're on the road | | Secure Credit Card Transactions via SMS messaging | | From Xilo Online www.xilo.com/mpos | +----------------------------------------------------+ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
