Testing proxy servers in 6.6.2/6.7

Nakia Brewer Nakia.Brewer at westrac.com.au
Thu May 8 18:51:35 EDT 2014

This is what I get

httpproxyforurl for host 'samaritans.org.au': 
Proxy for URL: 
socket selected: csu.harvestapp.com:443|6927
socket error csu.harvestapp.com:443|6927
Error 10061 on socket
httpproxyforurl for host 'samaritans.org.au': 
Proxy for URL: 
socket selected: csu.harvestapp.com:443|6928
socket error csu.harvestapp.com:443|6928
Error 10061 on socket
httpproxyforurl for host 'samaritans.org.au': 
Proxy for URL: 
socket selected: csu.harvestapp.com:443|6929
socket error csu.harvestapp.com:443|6929
Error 10061 on socket

Nakia Brewer | Technology & Solutions Manager | Equipment Management Solutions
t: (02) 49645051 | m: 0458 713 547 | i: www.westrac.com.au

  ACN 009 342 572

-----Original Message-----
From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf Of Trevor DeVore
Sent: Thursday, 8 May 2014 11:04 PM
To: How to use LiveCode
Subject: Re: Testing proxy servers in 6.6.2/6.7

On Wed, May 7, 2014 at 9:07 PM, Nakia Brewer <Nakia.Brewer at westrac.com.au>wrote:

> Okay so just tested in 6.6.2 RC3 and still no luck.
> Stack works fine if I take it off this network (away from a Proxy) or 
> if I use your work around Trevor...


Hmm, the other issue could be authentication. LiveCode isn't going to have authentication callbacks installed by default libURL may just be failing when the proxy server asks for authentication. If the authentication is BASIC or DIGEST then a person can write their own callbacks prompting the user for a username/password. If the authentication type is NTLM then it is a little more complex.

I just did a quick test with WonderProxy and see this in the libURL log:

_proxyForURL_proxyForURL use _proxyFromHTTPProxy() with HTTPProxyProxy for
URL: http://baltimore.wonderproxy.com:80
socket selected:|6924
GET http://www.google.com:80/ HTTP/1.1
Host: www.google.com
User-Agent: LiveCode (MacOS)

HTTP/1.1 407 Proxy Authentication Required
Server: squid/3.4.4
Mime-Version: 1.0
Date: Thu, 08 May 2014 13:01:36 GMT
Content-Type: text/html
Content-Length: 3318
Proxy-Authenticate: Basic realm="WonderProxy"
X-Cache: MISS from baltimore.wonderproxy.com
Via: 1.1 baltimore.wonderproxy.com (squid/3.4.4)
Connection: keep-alive

So the authentication part fails.

Can you turn on logging for lib URL and see if you can figure anything out from the diagnostics? Just create a stack with a field and tell libURL to log to it:

libURLSetLogField the long id of field 1 of stack "Untitled 1"

Do you see any authentication headers?

Trevor DeVore
Blue Mango Learning Systems
www.screensteps.com    -    www.clarify-it.com
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

COPYRIGHT / DISCLAIMER: This message and/or including attached files may contain confidential proprietary or privileged information. If you are not the intended recipient, you are strictly prohibited from using, reproducing, disclosing or distributing the information contained in this email without authorisation from WesTrac. If you have received this message in error please contact WesTrac on +61 8 9377 9444. We do not accept liability in connection with computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment. We reserve the right to monitor all e-mail communications.

More information about the Use-livecode mailing list