After some further digging, I solved this issue using the proxypage .NET approach.
Basically, you need to modify the proxy.ashx handler in the following way (C#.NET) - modifications in bold
*******************************************************************************
public void ProcessRequest(HttpContext context)
{
//Added code for passing your local webproxy
WebProxy proxyObject = new WebProxy("http://999.999.999.999:1234/", true);
NetworkCredential myCreds = new NetworkCredential("username", "password","domain");
proxyObject.Credentials = myCreds;
HttpResponse response = context.Response;
// Get the URL requested by the client (take the entire querystring at once
// to handle the case of the URL itself containing querystring parameters)
string uri = context.Request.Url.Query.Substring(1);
// Get token, if applicable, and append to the request
string token = getTokenFromConfigFile(uri);
if (!String.IsNullOrEmpty(token))
{
if (uri.Contains("?"))
uri += "&token=" + token;
else
uri += "?token=" + token;
}
System.Net.HttpWebRequest req = (System.Net.HttpWebRequest)System.Net.HttpWebRequest.Create(uri);
//Add proxy to your HttpWebRequest
req.Proxy = proxyObject;
req.Method = context.Request.HttpMethod;
req.ServicePoint.Expect100Continue = false;
req.Referer = context.Request.Headers["referer"];
..... code continued
*******************************************************************************
Hope this is useful to someone. It works out very well for me.
Jan