Re: XML RPC - automatically switch to ssl/https if port 443 is specified

No I wasn't initially specifying a protocol, which is where the problem came from, but it seems kind of inconsistent for the package to change the port to 443 if it sees https/ssl (it's assuming you want to run SSL over 443) and not go the other way. Everyone know of those commonly used ports and what protocols typically run over them. On Thu, 20 Jan 2005 09:24:38 -0800, Justin Patrin <papercrane@gmail.com> wrote: > On Thu, 20 Jan 2005 12:00:32 -0500, DreamWerx <dreamwerx@gmail.com> wrote: > > Internally in the sendPayload function, if XML-RPC sees a https/ssl > > prefix on the servername it will switch the port to 443, how about > > adding; if the function sees port 443 and there is no https/ssl prefix > > on the servername it will add it? > > > > I ran into a problem where I had port 443 configured and a hostname > > with no ssl:// prefix. I kept getting errors, with apache/mod_ssl > > debugging on, mod_ssl/openssl reported that I was attempting to talk > > HTTP on a HTTPS port.. Which helped resolve the misconfiguration. > > Are you giving it a protocol at all? IMHO if you say http:// > and port > 443 it should still try to talk HTTP. However, if you give no protocol > and posrt 443, it would make (some) sense to me to auto-switch to SSL, > but it makes even more sense to just use the https or ssl protocol > entry and forget the port. > > > > > Thoughts? > > > > BTW thanks for the quick RC3 fix yesterday... > > > > -- > Justin Patrin >