Maybe I misunderstand what you're getting at - but there is nothing in the xmlrpc code binding it to a specific port. It is wrapped in HTML requests though, so you need your webserver to respond with HTMl on the port you use.

tor wrote:

Maybe I misunderstand what you're getting at - but there is nothing in the xmlrpc code binding it to a specific port. It is wrapped in HTML requests though, so you need your webserver to respond with HTMl on the port you use.

The problem I'm referring to is when my b3evo installation attempts to connect to a *remote* xmlrpc service. This occurs in a few places; pings, antispam, etc. These remote services are configured on port 80; I have no control over those port and the University of Sydney enforces proxy usage by blocking port 80 (not an uncommon situation). Thus attempts to update the antispam list on my server fail. They need to be able to utilise a proxy to access these services.

Cheers,
Steve

Ok - I see, basically you'd like any http/https calls made from the server code to be able to use a proxy - or a configurable port number.

tor wrote:

Ok - I see, basically you'd like any http/https calls made from the server code to be able to use a proxy - or a configurable port number.

Well, a configurable port number isn't possible as I have no control over the configuration of the remote site. Remember, any connection from any port on my server to any port-80 anywhere on the internet is blocked. Another way to think of it is to say "all outgoing connections are blocked and must use a proxy" (a fairly common configuration with DMZ systems). Thus b2e needs to be able to utilise a proxy to do pings, antispam, etc.

Cheers,
Steve