On 2015-05-03 01:31, Dr. Hawkins wrote:
On Sat, May 2, 2015 at 2:33 PM, Mark Wieder <mwie...@ahsoftware.net>
wrote:
Try 'secure socket' rather than 'open socket' (v6.6 and above)
According to the dictionary in 7.0.4, secure socket is used after the
socket is opened.
It also causes a sudden crash of livecode itself when attempting to
execute
. . .
now bug 15314 <http://quality.runrev.com/show_bug.cgi?id=15314>
The 'secure' socket syntax was added to support SSL over HTTP proxies
which require an unencrypted stream to become a secure stream at a
specific point. (This method essentially means, even over a proxy, any
SSL stream is still between the two end-points, the proxy in the middle
just becomes a transport for the encrypted data on which it cannot
introspect).
It looks like you've hit a use-case which hasn't been tested - the proxy
case is always the client calling 'secure socket' (as the server - the
proxy - controls when it expects the SSL protocol to start). The example
you've posted won't work, as the both sides need to 'secure' at the same
time in the byte-stream - but it shouldn't crash :)
--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
