Ross,
Ross Ferris wrote:
"Secure" implies SSL, which as you identify means using "well known ports". I'd think it would take a lot more work to "bastardise" a solution using encrypted traffic on non-standard ports (I don't think you want to encrypt ALL traffic, so 80 won't do the trick) than changing your proxy to include SSL ports
HTTP proxying should work regardless of the proxy port -- you certainly can configure a proxy with different ports for http/https but I don't believe you need to (the proxy just has to understand the HTTP CONNECT method AFIK).
If callHTTP allows you to use a proxy, it should send all traffic there regardless of the destination port.
To confirm this was the problem, you could try using callHTTP to access a site on some non-standard port (eg: 8080) via the proxy and see if that works.
Craig ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
